@Article{hellwagner:pfs,
  author = {Hermann Hellwagner},
  title = {Design Considerations for Scalable Parallel File Systems},
  journal = {The Computer Journal},
  year = {1993},
  volume = {36},
  number = {8},
  pages = {741--755},
  keywords = {parallel I/O, multiprocessor file system, pario-bib},
  comment = {An overview of the issues in designing a parallel file system,
  along with some early ideas for their own file system. They aim for a
  general-purpose system, and characterize the workload into three classes:
  independent, much like a timesharing system; cooperative-agents, like that
  expected by most current MIMD file systems; and single-agent, for
  data-parallel programs where a ``master'' process issues single large
  requests on behalf of many processes. Their design is heavily weighted to the
  assumption of shared memory, and in particular to a randomized shared memory
  (like RP3), so they don't worry about locality much. They say little about
  their interface, although they intend to stick to a Unix interface --- and
  Unix semantics --- as much as possible. The file system is essentially
  represented by a collection of shared data structures and many threads to
  manipulate those structures.}
}