B. Pawlowski, S. Shepler, et al. The NFS Version 4 Protocol, in Proceedings of the 2nd international system administration and networking conference (SANE2000)  Home/Search   Document Details and Download   Summary   Related Articles   Check

....and I O. The Direct Access File System (DAFS) 6, 7] a new local file sharing standard, is designed to provide applications with high throughput, low latency access to shared file servers over memory to memory networks with VIcompliant capabilities. The DAFS Protocol is based on NFS version 4 [13], with new features for direct data transfer, asynchronous operations, scatter gather list I O, and locking and recovery features for a data center or cluster environment. It takes full advantage of memory to memory networks such as cLAN [8] with remote DMA support to provide high performance file ....

S. Shepler, B. Callaghan, D. Robinson, and et al. NFS Version 4 Protocol. RFC 3010, December 2000.

....allows the net work adapter to reduce copy overhead by accessing application buffers directly. The Direct Access File System (DAFS) 14] is a new standard for network attached storage over direct access transport networks. The DAFS protocol is based on the Network File System Version 4 protocol [32], with added protocol features for direct data transfer using RDMA, scatter gather list I O, reliable locking, command flow control and session recovery. DAFS is designed to enable a user level file system client: a DAFS client may run as an application library above the operating system kernel, ....

....The next section gives an overview of the DAFS architecture and standards, with an emphasis on the transport related aspects: Sections 3.2 and 3.3 focus on DAFS support for RDMA and asynchronous file I O respectively. 3. 1 DAFS Protocol Summary The DAFS protocol derives from NFS Version 4 [32] (NFSv4) but diverges from it in several sig nificant ways. DAFS assumes a reliable network transport and offers server directed command flowcontrol in a manner similar to block storage protocols such as iSCSI. In contrast to NFSv4, every DAFS operation is a separate request, but DAFS supports ....

[Article contains additional citation context not shown here]

S. Shepler, B. Callaghan, D. Robinson, R. Thurlow, C. Beame, M. Eisler, and D. Noveck. NFS Version 4 Protocol. RFC 3010, December 2000.

....of two techniques. The first, which we call directory subtree partitioning, partitions the namespace according to directory subtrees [6] In directory subtree partitioning, the metadata of complete directory trees is managed by individual metadata servers, analogous to directory mounting in NFS [14]. This technique suffers from severe bottleneck problems when a single file, directory, or directory subtree becomes popular. Furthermore, the directory hierarchy must be traversed to determine the permissions for each file that is accessed. This is often mitigated somewhat by client side prefix ....

B. Pawlowski, S. Shepler, C. Beame, B. Callaghan, M. Eisler, , D. Noveck, D. Robinson, and R. Thurlow. The NFS version 4 protocol. In Proceedings of the 2nd International System Administration and Networking Conference (SANE 2000.

....successfully for the Venti system [11] does not appear to hold for EECS or CAMPUS because even though cache sizes have increased since 1985, the size of file systems and the amount of data accessed by applications has also grown. We speculate that the NFSv4 lease and delegation mechanisms [10] could eliminate a large fraction of the NFS calls generated by the EECS workload by removing many of the situations where a client is contacting the server simply to confirm that its cached copy of a file is up to date. 6.1.2 The CAMPUS Workload Email On CAMPUS, email is the dominant cause of ....

B. Pawlowski, S. Shepler, C. Beame, B. Callaghan, M. Eisler, D. Noveck, D. Robinson, , and R. Thurlow. The NFS Version 4 Protocol. In Proceedings of the 2nd International System Administration and Networking Conference (SANE2000.

....allows the network adapter to reduce copy overhead by accessing application bu#ers directly. The Direct Access File System (DAFS) 14] is a new standard for network attached storage over direct access transport networks. The DAFS protocol is based on the Network File System Version 4 protocol [32], with added protocol features for direct data transfer using RDMA, scatter gather list I O, reliable locking, command flow control and session recovery. DAFS is designed to enable a user level file system client: a DAFS client may run as an application library above the operating system kernel, ....

....The next section gives an overview of the DAFS architecture and standards, with an emphasis on the transport related aspects: Sections 3.2 and 3.3 focus on DAFS support for RDMA and asynchronous file I O respectively. 3. 1 DAFS Protocol Summary The DAFS protocol derives from NFS Version 4 [32] (NFSv4) but diverges from it in several significant ways. DAFS assumes a reliable network transport and o#ers server directed command flowcontrol in a manner similar to block storage protocols such as iSCSI. In contrast to NFSv4, every DAFS operation is a separate request, but DAFS supports ....

[Article contains additional citation context not shown here]

S. Shepler, B. Callaghan, D. Robinson, R. Thurlow, C. Beame, M. Eisler, and D. Noveck. NFS Version 4 Protocol. RFC 3010, December 2000.

....a security layer on top of NFS. These include proposals to secure the RPC [Taylor86] and tunnelling NFS through SSH or SSL [Gerraty99] to protect data on the wire. The security assumptions and implications of these systems closely match those of AFS and NASD. The recent NFSv4 specification [Shepler00] explicitly addresses the problem of securing the RPC mechanism. Currently it proposes at least three security mechanisms: one using Kerberos and two using a public key infra 11 structure. All these essentially set up a secure communication channel and enable mutual authentication. ....

S. Shepler, B. Callaghan, D. Robinson, R. Thurlow, C. Beame, M. Eisler and D. Noveck. NFS Version 4 Protocol. RFC 3010, December 2000.

....operating systems by # Supported by NSERC PGSB Supported by NSERC PGSA careful refactoring. This short paper focuses on a preliminary but representative example of evolution associated with an individual v4 feature, and extrapolates from our experience so far. As the Java prototype of NFSv4 [6] has not yet been released, we implemented our own Java model of NFSv3, JNFS [3] and evolved it. The feature we focus on is our own client specific policy for fault tolerance built on top of v4 s support for replication. The characteristics we extrapolate are those associated with aspects that we ....

Brian Pawlowski, Spencer Shepler, Carl Beame, Brent Callaghan, Michael Eisler, David Noveck, David Robinson, and Robert Thurlow. The nfs version 4 protocol. In International SANE

....performance analysis is based on the execution of the Andrew file system benchmark (AB [7] on directories mounted through PVFS. This 6 To overcome this problem, the next version of NFS (v4) will retire the mount protocol and allow file system connections that do not involve the port mapper [15]. benchmark consists of a sequence of Unix commands of different types (directory creation, file copying, file searching, and compilation) that models a workload typical of a software development environment. The experimental setup consists of the set of machines described in Table 1. These ....

....have been extensively exercised during normal use of PUNCH by its users. It has been found to perform well, with an average overhead of 18 or less over the native NFS. Future work will investigate virtual file system solutions based on next generation protocols (e.g. the next version of NFS [15]) that are designed to operate with high performance across high latency, low bandwidth links in wide area networks. Acknowledgements This work was partially funded by the National Science Foundation under grants EEC 9700762, ECS9809520, EIA 9872516, and EIA 9975275, and by an academic ....

B. Pawlowski, S. Shepler, C. Beame, B. Callaghan, M. Eisler, D. Noveck, D. Robinson, and R. Thurlow. The NFS version 4 protocol. In Proceedings of Second International System Administration and Networking (SANE) Conference, May 2000.

No context found.

B. Pawlowski, S. Shepler, et al. The NFS Version 4 Protocol, in Proceedings of the 2nd international system administration and networking conference (SANE2000)

No context found.

Pawlowski, B., Shepler, S., Beame, C., Callaghan, B., Eisler, M., Noveck, D., Robinson, D., Thurlow, R. The NFS Version 4 Protocol. Proceedings of the 2nd international system administration and networking conference (2000)

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