@TechReport{Dartmouth:TR96-286,
  author = {Nils Nieuwejaar and David Kotz},
  title = {{The Galley Parallel File System}},
  institution = {Dartmouth College, Computer Science},
  address = {Hanover, NH},
  number = {PCS-TR96-286},
  year = {1996},
  month = {May},
  URL = {http://www.cs.dartmouth.edu/reports/TR96-286.ps.Z},
  comment = {
    Revised version appeared in the journal
    <a href="/~dfk/papers/jgalley.html">Parallel Computing</a>.
    This paper is a combination of two papers, from 
    <a href="/~dfk/papers/galley.html">ICS '96</a> 
    and a
    <a href="/~dfk/papers/galley-perf.html">IOPADS '96</a>.
  },
  abstract = {
    Most current multiprocessor file systems are designed to use multiple
    disks in parallel, using the high aggregate bandwidth to meet the growing
    I/O requirements of parallel scientific applications. Many multiprocessor
    file systems provide applications with a conventional Unix-like
    interface, allowing the application to access multiple disks
    transparently.  This interface conceals the parallelism within the file
    system, increasing the ease of programmability, but making it difficult
    or impossible for sophisticated programmers and libraries to use
    knowledge about their I/O needs to exploit that parallelism.  In addition
    to providing an insufficient interface, most current multiprocessor file
    systems are optimized for a different workload than they are being asked
    to support.  We introduce Galley, a new parallel file system that is
    intended to efficiently support realistic scientific multiprocessor
    workloads. We discuss Galley's file structure and application interface,
    as well as the performance advantages offered by that interface.
  }
}