@Manual{chapple:pario,
  author = {S. R. Chapple and R. A. Fletcher},
  title = {{PUL-GF} Parallel {I/O} Concepts},
  year = {1993},
  month = {February},
  organization = {Edinburgh Parallel Computing Center},
  note = {EPCC-KTP-PUL-GF-PROT-CONC 1.0},
  URL = {file://ftp.epcc.ed.ac.uk/pub/pul/concepts-i.ps},
  keywords = {parallel I/O, pario-bib},
  comment = {See also bruce:chimp, chapple:pulgf, and chapple:pulgf-adv, for
  general information on CHIMP and PUL-GF. This document is an exploration of
  the potential ways to parallelize the underlying I/O support for the PUL-GF
  interface. They reason about tradeoffs in the number of servers, disks, and
  clients, but (as they note) without any performance evaluation to back it up.
  In particular, they argue that there should be one partition per disk, one
  server per disk, and probably one client to many servers, or many clients to
  many servers. A key assumption is that a traditional serial file system is
  the home location for files, and that files are ``converted'' into parallel
  files (or vice versa) by replicating or distributing them. Application could
  choose the number of servers (and hence disks) for each file. Hints could be
  provided about many things. Interesting idea to allow user hooks for cache
  prefetch and writeback functions. Support for variable-length records
  (``atoms'') is a key component. Segments of a file with different formats,
  e.g., a header and a matrix, may be separated into different components when
  the file is distributed into parallel form. See chapple:pulpf for info on the
  eventual realization of these ideas.}
}