Proceedings of the Fifth Workshop on I/O in Parallel and Distributed Systems - IOPADS '97 1997
DOI: 10.1145/266220.266222
|View full text |Cite
|
Sign up to set email alerts
|

Remote I/O

Abstract: As high-speed networks make it easier to use distributed resources, it becomes increasingly common that applications and their data are not colocated.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2001
2001
2010
2010

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 58 publications
(2 citation statements)
references
References 21 publications
(14 reference statements)
0
2
0
Order By: Relevance
“…The user-level SIOS is implemented with I/O service routines or libraries. The Parallel Virtual File System [6], and the remote I/O project [11] are typical examples of user-level SIOS. This approach has two shortcomings: First, users have to apply specific APIs and identifiers to explore parallelism in I/O.…”
Section: Single I/o Spacementioning
confidence: 99%
“…The user-level SIOS is implemented with I/O service routines or libraries. The Parallel Virtual File System [6], and the remote I/O project [11] are typical examples of user-level SIOS. This approach has two shortcomings: First, users have to apply specific APIs and identifiers to explore parallelism in I/O.…”
Section: Single I/o Spacementioning
confidence: 99%
“…Parallel I/O systems commonly treat access to distributed data as a collective operation [49], and collective communication operations seek to optimize data transformations and transfers by coordinating related activities [35,38]. In two-phase I/O [48] and in Remote I/O [25], data is read and then reorganized via interprocess communication prior to transfer. HPF/MPI [21] used the FALLS (FAmiLy of Line Segments) representation [47] to compute efficient inter-cluster communication schedules.…”
Section: Related Workmentioning
confidence: 99%