@InProceedings{philippsen:triton,
  author = {Michael Philippsen and Thomas M. Warschko and Walter F. Tichy and
  Christian G. Herter},
  title = {{Project Triton:} Towards improved Programmability of Parallel
  Machines},
  booktitle = {Proceedings of the Twenty-Sixth Annual Hawaii International
  Conference on System Sciences},
  year = {1993},
  volume = {I},
  pages = {192--201},
  keywords = {parallel programming, parallel architecture, parallel I/O,
  pario-bib},
  comment = {A language- and application-driven proposal for parallel
  architecture, that mixes SIMD and MIMD, high-performance networking, large
  memory, shared address space, and so forth. Fairly convincing arguments. One
  disk per node. Little mention of a file system though. Email from student Udo
  Boehm:``We use in the version of Triton/1 with 256 PE's 72 Disks at the
  moment (the filesystem is scalable up to 256 Disks). These Disks are divided
  into 8 Groups with 9 Disks. In each group exists one parity disk. Our
  implementation of the filesystem is an parallel version of RAID Level 3 with
  some extensions. We use so called vector files for diskaccess. A file is
  always distributed over all disks of the diskarray. A vectorfile is divided
  in logical blocks. A logical block exist of 72 physical blocks, each block is
  on one of the 72 disks and all these 72 physical blocks have the same
  blocknumber on each disk. A logical block has 18432 Bytes, where 16384 Bytes
  are for Data. The filesystem uses these logical blocks to save data. We do
  not use special PE's for the I/O. All PE's can be (are) used to do I/O !
  There exists no central which coordinates the PE's.''}
}