David Cheriton. UIO: A uniform I/O system interface for distributed systems. ACM Transactions on Computer Systems, 5(1):12--46, February 1987. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Exploiting Mapped Files for Parallel I/O - Krieger, Reid, Stumm (1995) (1 citation) (Correct)
....In contrast, read write interfaces like Unix I O allow applications to use the same operations whether the I O is directed to a file, terminal or network connection. Such a uniform I O interface allows a program to be independent of the type of data sources and sinks with which it communicates [2]. Another problem with the mapped file I O interface is that it is very different from more popular I O interfaces like Unix I O, and applications written to use these interfaces have to be rewritten to exploit the advantages of mapped file I O. Other parallel I O interfaces are provided as ....
D. Cheriton. UIO: A Uniform I/O system interface for distributed systems. ACM Transactions on Computer Systems, 5(1):12--46, February 1987.
HFS: A flexible file system for shared-memory multiprocessors - Krieger (1994) (17 citations) (Correct)
....including disk files, terminals, pipes, networking interfaces and other low level devices. We refer to an interface that can be used in this fashion as a uniform I O interface. Uniform I O interfaces allow programs to be independent of the type of data sources and sinks with which they communicate [21]. open( filename, mode ) opens a stream read( stream, buffer, nbytes ) reads nbytes from the current stream offset into buffer and increments the stream offset by nbytes write( stream, buffer, nbytes ) writes nbytes from buffer to the current stream offset and increments the stream offset ....
....to hold a lock on the stream from the time of the lseek operation until the corresponding I O operation has completed, effectively serializing I O operations. Other read write interfaces Other read write interfaces overcome some of the limitationsof Unix I O. For example, Cheriton sUIO interface [21] (i) allows different threads to make random I O requests without interference, ii) takes into account the block size of the requested service, and (iii) returns thread specific errors. Also, many Unix systems (e.g. IRIX version 5.1 and SunOS) provide asynchronous I O facilities that allow ....
[Article contains additional citation context not shown here]
D. Cheriton. UIO: A Uniform I/O system interface for distributed systems. ACM Transactions on Computer Systems, 5(1):12--46, February 1987.
The Alloc Stream Facility: A Redesign of Application-Level .. - Krieger, Stumm, Unrau (1994) (15 citations) (Correct)
.... read, write, seek, close, and ioctl (See Figure 1) The Unix I O facility is simple, easy to use, and has proven to be versatile in that it can be applied in a uniform way to a large variety of I O services, including disk files, terminals, pipes, networking interfaces and other low level devices [Che87] Nevertheless, application programs running under Unix typically do not call the Unix I O system calls directly, but instead use higher level facilities implemented either by the programming language (e.g. Pascal, Fortran, and Ada) or by application level libraries associated with the open( ....
D. Cheriton. UIO: A Uniform I/O System Interface for Distributed Systems. ACM Transactions on Computer Systems, 5(1):12--46, February 1987.
Decentralizing a Global Naming Service for Improved.. - Cheriton, Mann (1989) (39 citations) Self-citation (Cheriton) (Correct)
....to succeed if it communicates with at least one subobject manager. Any additional protocol required to communicate with other managers for consistent access or update is object type specific; it is implemented by the subobject managers, not by the naming system. For example, in the UIO interface [6], each manager of a replicated object maintains a list of the other managers storing replicas. 21 4.2 Query We discuss two query operations in this section: binding check and directory listing. The binding check operation takes a name n and returns the name s binding status (bound or unbound) ....
D. R. Cheriton. UIO: A uniform I/O system interface for distributed systems. ACM Transactions on Computer Systems, 5(1):12--46, February 1987.
Coordinating Access to Computation and Data in Distributed Systems - Thain (2004) (Correct)
No context found.
David Cheriton. UIO: A uniform I/O system interface for distributed systems. ACM Transactions on Computer Systems, 5(1):12--46, February 1987.
Coordinating Access to Computation and Data in Distributed Systems - Thain (2004) (Correct)
No context found.
David Cheriton. UIO: A uniform I/O system interface for distributed systems. ACM Transactions on Computer Systems, 5(1):12--46, February 1987.
Parrot: An Application Environment for Data-Intensive Computing - Thain, Livny (Correct)
No context found.
D. Cheriton, UIO: A uniform I/O system interface for distributed systems, ACM Transactions on Computer Systems, 5 (1987), pp. 12--46.
Parrot: Transparent User-Level Middleware for Data Intensive.. - Thain, Livny (2003) (Correct)
No context found.
D. Cheriton. UIO: A uniform I/O system interface for distributed systems. ACM Transactions on Computer Systems, 5(1):12--46, February 1987.
Parrot: An Application Environment for Data-Intensive Computing - Thain, Livny (Correct)
No context found.
D. Cheriton, UIO: A uniform I/O system interface for distributed systems, ACM Transactions on Computer Systems, 5 (1987), pp. 12--46.
Parrot: Transparent User-Level Middleware for Data-Intensive.. - Thain, Livny (2003) (Correct)
No context found.
D. Cheriton. UIO: A uniform I/O system interface for distributed systems. ACM Transactions on Computer Systems, 5(1):12--46, February 1987.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC