diff -r pario/web/bibtex/barve:mergesort.bib pario/web/new/barve:mergesort.bib
3a4,5
>   booktitle = {Proceedings of the Eighth Symposium on Parallel Algorithms and
>   Architectures},
diff -r pario/web/bibtex/bordawekar:collective.bib pario/web/new/bordawekar:collective.bib
1c1
< @TechReport{bordawekar:collective,
---
> @InProceedings{bordawekar:collective,
3,26c3,15
<   title = {Implementation and Evaluation of Collective {I/O} in the {Intel
<   Paragon Parallel File System}},
<   year = {1996},
<   month = {November},
<   number = {CACR~TR-128},
<   institution = {Center of Advanced Computing Research, California Insititute
<   of Technology},
<   URL = {http://www.cacr.caltech.edu/~rajesh/collective.html},
<   keyword = {parallel I/O, mutliprocessor file system, pario-bib},
<   abstract = {A majority of parallel applications obtain parallelism by
<   partitioning data over multiple processors. Accessing distributed data
<   structures like arrays from files often requires each processor to make a
<   large number of small non-contiguous data requests. This problem can be
<   addressed by replacing small non-contiguous requests by large collective
<   requests. This approach, known as Collective I/O, has been found to work
<   extremely well in practice. In this paper, we describe implementation and
<   evaluation of a collective I/O prototype in a production parallel file system
<   on the Intel Paragon. The prototype is implemented in the PFS subsystem of
<   the Intel Paragon Operating System. We evaluate the collective I/O
<   performance using its comparison with the PFS M_RECORD and M_UNIX I/O modes.
<   It is observed that collective I/O provides significant performance
<   improvement over accesses in M_UNIX mode. However, in many cases, various
<   implementation overheads cause collective I/O to provide lower performance
<   than the M_RECORD I/O mode.}
---
>   title = {Implementation of Collective {I/O} in the {Intel Paragon} Parallel
>   File System: Initial Experiences},
>   booktitle = {Proceedings of the 11th ACM International Conference on
>   Supercomputing},
>   year = {1997},
>   month = {July},
>   publisher = {ACM Press},
>   earlier = {bordawekar:collective-tr},
>   URL = {http://www.cacr.caltech.edu/~rajesh/ics97.ps},
>   keyword = {verify pages, collective I/O, multiprocessor file system, parallel
>   I/O, pario-bib},
>   comment = {bordawekar:collective was renamed bordawekar:collective-tr, so
>   this could be called bordawekar:collective.}
diff -r pario/web/bibtex/sanders:datatypes.bib pario/web/new/sanders:datatypes.bib
16c16,24
<   behavior of MPI datatypes in a heterogenous environment is not well-defined.}
---
>   behavior of MPI datatypes in a heterogenous environment is not
>   well-defined.},
>   comment = {They devise several file-access strategies for different
>   situations, depending on the particulars of the etypes and filetypes in use:
>   sequential, two-phase I/O, one file access per etype (random access), and one
>   file access per etype element (random access with smaller pieces). They
>   measure the performance of their system with example patterns that trigger
>   each strategy. It would be nice to see a more extensive performance analysis
>   of their implementation, and of their strategies.}
diff -r pario/web/bibtex/vengroff:tpie-man.bib pario/web/new/vengroff:tpie-man.bib
7c7
<   http://www.cs.duke.edu/~dev/tpie_home_page.html},
---
>   http://www.cs.duke.edu/\~{}dev/tpie_home_page.html},