BibTeX for a paper by David Kotz at Dartmouth College.
For more information about this paper, visit this web page:
https://kotz.cs.dartmouth.edu/research/kotz-flexibility2/index.html

@InProceedings{kotz:flexibility2,
  author =        {David Kotz and Nils Nieuwejaar},
  title =         {{Flexibility and Performance of Parallel File Systems}},
  booktitle =     {{Proceedings of the International Conference of the Austrian Center for Parallel Computation (ACPC)}},
  series =        {Lecture Notes in Computer Science},
  year =          1996,
  month =         {September},
  volume =        1127,
  pages =         {1--11},
  publisher =     {Springer},
  copyright =     {Springer},
  DOI =           {10.1007/3-540-61695-0_1},
  URL =           {https://kotz.cs.dartmouth.edu/research/kotz-flexibility2/index.html},
  note =          {Invited paper},
  abstract =      {As we gain experience with parallel file systems, it becomes increasingly clear that a single solution does not suit all applications. For example, it appears to be impossible to find a single appropriate interface, caching policy, file structure, or disk-management strategy. Furthermore, the proliferation of file-system interfaces and abstractions make applications difficult to port. \par  We propose that the traditional functionality of parallel file systems be separated into two components: a fixed core that is standard on all platforms, encapsulating only primitive abstractions and interfaces, and a set of high-level libraries to provide a variety of abstractions and application-programmer interfaces (APIs). \par  We present our current and next-generation file systems as examples of this structure. Their features, such as a three-dimensional file structure, strided read and write interfaces, and I/O-node programs, re specifically designed with the flexibility and performance necessary to support a wide range of applications.},
}