diff -r pario/web/bibtex/chen:panda-model.bib pario/web/new/chen:panda-model.bib
22c22,33
<   comment = {Web and CDROM only.}
---
>   comment = {On Web and CDROM only. They derive a detailed but fairly simple
>   model of the Panda 2.0.5 parallel I/O library, by carefully enumerating the
>   costs involved in a collective I/O operation. They measure Panda, AIX, and
>   MPI to obtain parameters, and then they validate the model by comparison with
>   the actual Panda implementation running a basic benchmark and an actual
>   application. The model predicts the benchmark performance very well, and is
>   as much as 20\% off on the performance of the application. They have embedded
>   the performance model in a "simulator", which predicts the performance of a
>   given sequence of collective I/O requests, and they plan to use it in future
>   versions of Panda to formulate I/O plans by predicting the performance
>   resulting from several different Panda parameter settings, and choosing the
>   best.}
diff -r pario/web/bibtex/gibson:nasd-tr.bib pario/web/new/gibson:nasd-tr.bib
13c13,28
<   comment = {See http://www.cs.cmu.edu/Groups/NASD/ARPA96/server.html}
---
>   comment = {See http://www.cs.cmu.edu/Groups/NASD/ARPA96/server.html. They
>   outline their rationale for the idea of Network-attached Secure Disks (NASD).
>   Basically the idea is to develop disk drives that attach right to the LAN,
>   rather than to a file server, and allow clients to access the disks directly
>   for many of the simpler file system actions (read and write file data, read
>   file attributes), and only contact the server for more complex activities
>   (opening and creating files, changing attributes). This removes the load from
>   file servers, which are getting too slow to move large amounts of data needed
>   by large installations. Issues include security, of course, which they solve
>   with encryption (for privacy) and time-limited capabilities (keys) given out
>   by the server to authenticated clients, which the clients show to the disk to
>   gain access. They compare the performance of NASD, using a simple analytical
>   model and parameters obtained from measuring real NFS and AFS
>   implementations, to the performance of SAD (server-attached disks) and
>   NetSCSI (a hybrid approach that involves the server in every operation but
>   allows data to flow directly from disk to and from the network).}
diff -r pario/web/bibtex/kotz:fsint2p.bib pario/web/new/kotz:fsint2p.bib
8a9
>   URL = {ftp://ftp.cs.dartmouth.edu/pub/kotz/papers/kotz:fsint2p.ps.Z},
diff -r pario/web/bibtex/park:interface.bib pario/web/new/park:interface.bib
23c23,37
<   comment = {Web and CDROM only.}
---
>   comment = {Web and CDROM only. They advocate the use of traditional
>   demand-paged virtual memory systems in supporting out-of-core applications.
>   They are implementing an operating system for the NEC Cenju-3/DE, a
>   shared-nothing MIMD multiprocessor with a multistage interconnection network
>   and disks on every node. The operating system is based on Mach, and they have
>   extended Mach to allow user-provided [local] replacement policies. Basically,
>   they argue that you can get good performance as long as you write your own
>   replacement policy (even OPT is possible in certain applications), and that
>   this is easier than (re)writing the application with explicit out-of-core
>   file I/O calls. They measure the performance of two applications on their
>   system, with OPT, FIFO, and a new replacement algorithm customized to one of
>   the applications. They show that they can get much better performance with
>   some replacement policies than with others, but despite the paper's title
>   they do not compare with the performance of an equivalent program using file
>   I/O.}
diff -r pario/web/bibtex/womble:intro.bib pario/web/new/womble:intro.bib
11c11,17
<   keyword = {parallel I/O, pario-bib}
---
>   keyword = {parallel I/O, pario-bib},
>   comment = {A brief introduction to the topic of parallel I/O (what, why,
>   current research), followed by a roundtable discussion among the authors of
>   the papers in womble:special-issue. The discussion focused on three
>   questions: 1) What are the biggest gaps in current I/O services? 2) Why have
>   vendors failed to adopt new file system technologies? 3) How much direct
>   low-level control over I/O resources should be given to the users and why?}
diff -r pario/web/bibtex/womble:special-issue.bib pario/web/new/womble:special-issue.bib
12c12,17
<   keyword = {parallel I/O, pario-bib}
---
>   keyword = {parallel I/O, pario-bib},
>   comment = {A one-page introduction to this special issue of Parallel
>   Computing, which includes many papers about parallel I/O. See also
>   womble:intro, nieuwejaar:jgalley, moore:ddio, barve:jmergesort, miller:jrama,
>   schwabe:jlayouts, parsons:templates, cormen:early-vic,
>   carretero:performance,}