Sun Microsystems. NFS: network file system protocol specification, RFC--1094, March 1989.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....1,150 14,088 95 Static Credit 1,600 16,083 95 Allocation (N3=30) N3=30) Figure 13) 2,300 13,272 (N3=40) N3 40) Table 2: Performance comparisons between adaptive and static credit allocation 12. Simulation Suite D: NFS 12.1. Simulation Configuration The simulation configuration for NFS [16] traffic is depicted in Figure 17. Clients on the right hand side issues read requests to the servers on the left hand side. The figure shows 80 VCs each carrying data responding to requests carried on paired VCs from right to left; the traffic on client to server VCs is small. NFS traffic is ....

Sun Microsystems. "NFS: Network File System Protocol Specification," RFC 1094, Mar 1988.

....may be a useful trade off point. 5 Storage based intrusion detection in an NFS server To explore the concepts and feasibility of storage based intrusion detection, we implemented a storage IDS in an NFS server. Unmodified client systems access the server using the standard NFS version 2 protocol [40] , while storagebased intrusion detection occurs transparently. This section describes how the prototype storage IDS handles detection rule specification, the structures and algorithms for checking rules, and alert generation. The base NFS server is called S4, and its implementation is ....

Sun Microsystems. NFS: network file system protocol specification, RFC--1094, March 1989.

....is modified to provide the packet redirector information for deciding which packets should be redirected. Depending on the application, there are different ways of doing it. The first way is to let the application notify the packet redirector which replies contain dummy data. For example, an NFS [22] server can notify the packet redirector that a particular NFS reply contains dummy data by specifying the reply s RPC XID and client IP address (the XID is guaranteed to be unique for each NFS request from one client) The second way is to let the application provide the packet redirector with ....

Sun Microsystems Inc. NFS:Network File System Protocol Specification. IETF RFC 1094, March 1989.

....formats. In the Linux kernel, for example, data is stored in the format of sk buff in the network stack, and as contiguous buffer chunks in the page buffer cache, which are accessed by the NFS server. When a read like NFS request, including ROOT, GETATTR, LOOKUP, READLINK, READ, READDIR and STATFS [6], arrives at the NFS server, it services the request by reading the requested data from the page buffer cache in the local file system. If the content happens to be cached in the buffer page cache, the local file system copies the data directly to the NFS server. Otherwise, a disk access request ....

....module obtains the requested data, it composes an NFS reply and sends it out using Remote Procedure Call (RPC) protocol. Sending the replies out incurs one more data copying from the NFS server module to the network stack. For a write like NFS request, such as SETATTR, WRITECACHE, WRITE and MKDIR [6], the same number of data copying operations is required within the NFS server. When an NFS write like request arrives, the content stored in the request is first copied from the network stack into the NFS server module, which then writes the data into the page cache of the local file system. In ....

[Article contains additional citation context not shown here]

S. Microsystems. Nfs: Network file system protocol specification. IETF RFC 1094, March 1989.

....routines for handling requests. The remainder of this section describes the Cuckoo NFS server and describes how it offloads operations. 4. 1 The Cuckoo NFS server The prototype Cuckoo NFS server is built into an updated version of the S user level NFS server [21] and supports NFS version 2 [23]. Cuckoo has no dependency on the particular features of S and could be implemented, in the fashion described here, in most NFS servers. This particular user level NFS server implementation was chosen primarily for ready access to the authors. Cuckoo was implemented by adding additional data ....

Sun Microsystems, Inc. NFS: network file system protocol specification. Network Working Group, RFC--1094, March 1989.

....system was designed and implemented. The prototype acts as a self securing NFS server. It maintains an audit log and history pool as described above. The prototype runs as a user level process on the Linux operating system. Unmodified client systems can use the server as a standard NFS version 2 [30] server, while the self securing storage features are provided transparently. Our previous work [29] evaluated the two main costs of self securing storage: space con sumption of the history pool and performance overhead of comprehensive versioning. To evaluate the space consumption, the write ....

Sun Microsystems. NFS: network file system protocol specification, RFC 1094, March 1989.

....model implemented by the Amoeba file service has inspired the access control model used in capability file names. An important difference between the two systems is that capability file names are designed to ensure compatibility with existing applications, while Amoeba is not. 2. 3 NFS In NFS [34, 37], the server trusts the identification performed by the client. Clients and servers coordinate their user identifiers. File systems are explicitly exported to a designated set of clients. In order to access a file on the server, the user must be defined as a user on the server machine and the ....

Sun Microsystems Inc. NFS: Network file system protocol specification. Request for Comments (RFC) 1094, Network Working Group, March 1989.

....objects. Associative access is provided via traditional file system interfaces and other access methods. The system block diagram in figure 1 shows the basic building blocks of a prototype semantic file system [5] This semantic file system implementation uses the Network File System protocol [6], but interprets the file pathnames as Content Names. The dynamic interpretation of content names by the file storage system allows users to communicate with each other more easily. Inter user communications can involve content names, and these content names are correctly interpreted by the ....

Sun Microsystems. NFS: Network File System Protocol Specification. Technical Report Request for Comments (RFC 1094) Version 2, Network Working Group, Sunnyvale California, March 1989.

....Counting replugger Boolean replugger Invocation overhead 48 60 4 Replugging overhead 50 340 340 11 terpreting Berkeley Packet Filter (BPF) programs [36] and the Linux signal delivery mechanism. 4. 1 Specializing remote procedure calls Remote procedure call (RPC) is the basis for NFS [53], NIS [46, 55] and other Internet services. At the heart of Sun RPC is the eXternal Data Representation (XDR) standard which is a machine independent format for passing RPC parameters. The process of translating into and out of XDR is called marshaling. Marshaling is a key source of overhead in ....

Sun Microsystems, NFS: Network File System Protocol Specification, 1988,

....work in Linux and made changes only to the NFS server code; client side NFS and the NFS protocol remain unchanged. Our evaluation shows a minimal average performance overhead and, in some cases, an end to end performance improvement. 1 Introduction NFS was originally designed for use with LANs [17, 22], where a single administrative entity was assumed to control all of the hosts in that site and create unique user accounts and groups. The access model chosen for exporting NFS volumes was simple but weak. In a different administrative domain, the password database may define different users with ....

....of the 2002 Annual Usenix Technical Conference, FreeNIX track. Although NFSv4 [19] promises to provide strong authentication and provides a convenient framework for fixing these problems, it will not be available for many platforms and in wide use for several years. The transition between NFSv2 [22] and NFSv3 [2] took around 10 years and corresponds to relatively small changes compared to the changes between NFSv3 and NFSv4. Even today, NFSv3 is not fully implemented on all platforms. Moreover, the NFSv4 specification does not address all of the problems that we wish to fix. Nevertheless, ....

[Article contains additional citation context not shown here]

Sun Microsystems. NFS: Network file system protocol specification. Technical Report RFC 1094, Network Working Group, March 1989.

....this distributed file system architecture, a federated file system(FedFS) The simplest way to describe a federated file system is as a per application global file naming facility that the application can use to access files in the cluster in a location independent manner. By contrast, the NFS [3] solution of crossmounting remote file systems into local file systems will allow applications to access files through a location transparent, but not location independent manner (files have their location implicitly embedded in the pathname through the mounting directory) Using the proposed ....

....Similarly, A3 is distributed across nodes 2, 3 and 4 and uses FedFS2. In this example, the local file system of node 2 is part of two federated file systems. A1 runs only on node 1 and uses the local file system directly. There is a significant body of research related to distributed file systems [4, 5, 3, 6, 7, 8, 9, 10, 1, 2, 11, 12]. Some recent projects include [13] the emerging industry standard DAFS [14] and wide area systems like [16, 17, 18, 19] In our project, we combine two technologies: the federated file system idea, and the remote memory communication support. Remote memory communication is the key ingredient of ....

Sun Microsystems, Inc. NFS: Network File System Protocol Specification. RFC 1094 (1989).

....in more detail in the following sections. 2.2.1 Phase 1: Mobile File Systems Hosts in distributed computing environments often rely on the network in order to access shared resources, including the file system. Indeed, with distributed filing systems such as the Network File System (NFS) Sun,89] and Andrew File System (AFS) Satyanarayanan,85] it is possible for hosts to share files which are remotely located with other hosts. In the case of diskless workstations, all applications and data are implicitly located on remote filestore. Thus, when the network is unavailable or offering only ....

Sun Microsystems, "NFS: Network File System Protocol Specification", Request for Comments (RFC) number 1094, Sun Microsystems, 1989.

....more users adopt SANs and as SAN standards evolve. Today, with multiple operating systems and multiple vendor platforms present in most data centers, SAN inter operability is highly valued. NAS technologies, on the other hand, are mature and interoperable. They use defacto standards such as NFS[1] and CIFS[2] to provide data access. NFS clients are available for almost all platforms. Both NFS and CIFS have mechanisms to control and synchronize simultaneous access to shared data. These inherent features of NAS were taken advantage of in the design of DirectNFS. A simple way of using ....

Sun Microsystems, NFS: Network File System Protocol Specification, Request for Comments 1094, 1988.

....is modified to provide the packet redirector information for deciding which packets should be redirected. Depending on the application, there are different ways of doing it. One way is to let the application notify the packet redirector which replies contain dummy data. For example, an NFS [22] server can notify the packet redirector that a particular NFS reply contains dummy data by using the reply s RPC XID and client IP address (the XID is guaranteed to be unique for each NFS request from one client) Another way is to let the application provide the packet redirector with low level ....

Sun Microsystems Inc. NFS:Network File System Protocol Specification. IETF RFC 1094, Mar. 1989.

....links in Gopherspace were improved, Gopherspace might begin to resemble theWeb. We believe it is not so muchthe added functionality of WWW, butrather its flashyuserinterface (Mosaic) thathas lured users away from Gopher. 4.5. Extended Networked File Systems: Alex, WWFS, Prospero, NFS[Sun Microsystems, 1989] (Network File System) and AFS[Deutsch, 1992a,Satyanarayanan, 1990] Andrew File System) are widely used protocols that allow remote file systems toappear tobemounted onto a local file system. AFS supports cachingto providebetter performance than NFS, butotherwise they are very similar from the ....

Sun Microsystems (1989). NFS: Network File System protocol specification. RFC 1094.

....in Japan. These systems have many registered users more than 10; 000 and hundreds of client workstations for students. Most of those systems maintain the users personal data contents and public data like educational materials and large size programs using distributed file systems [1] 2] like NFS [3] or AFS [4] These data are stored in one or more file servers. When a user uses his data, his station accesses the file server through the LAN. In such educational systems, however, concentrated network access caused by many users operations affects the performance of the LAN. Accurate ....

....assumed the following conditions. # The Ready, Go Situation at educational computer network systems. # Six types of Ethernet LAN[7] consisting of one file server and N#= 1 # 150# clients. # Two types of file transfer application programs: FTP (File Transfer Protocol) 8] and NFS version 2[3]. # 1 MB file transferring from one server to N clients. The file size is selected to be the same as the size of a large size application program. We did not simulate file transmission from clients to a file server. Of course such a situation can take place on educational systems, however, file ....

Sun Microsystems, Inc., "NFS: network file system protocol specification," RFC 1094, 1989

....Moreover, if the networks are fast enough, it is possible to run a user level file system even on another machine by Remote Procedure Call (RPC) 18] with a socket. In this case, we do not have to create both a client and a server for the network file system like Sun Network File System (NFS) [19, 6], so we can make the user level file system faster. Using a socket is, however, di#cult for some reasons, in fact. There are two di#culties. One is the fact that a socket is more complicated than a signal. The complexity of a socket causes the performance of upcall to be reduced. The other is ....

Sun Microsystems, Inc., "NFS: Network File System Protocol Specification," RFC 1094, Network Information Center, SRI International, Mar. 1989. 40 Appendix A A program for our experiment The following program is the program that we used for measuring the performance

....have changed the kernel s client side NFS implementation, and outside the operating system we have made use of the Amd automounter and the RLP resource location protocol. Each is explained briefly below. 2. 1 NFS Particulars about the NFS protocol and implementation are widely known and published [Blaze92, Hitz94, Juszczak89, Juszczak94, Keith90, Keith93, Kleiman86, Macklem91, Pawlowski94, Rosen86, Rosenthal90, Sandberg85a, Sandberg85b, Schaps93, Srinivasan89, Stein87, Stern92, Sun85, Sun86, Sun89, Walsh85, Watson92]. For the purpose of our presentation, the only uncommon facts that need to be known are: Translation of a path name to a vnode is done mostly within a single procedure, called au lookuppn( that is responsible for detecting and expanding symbolic links and for detecting and crossing mount ....

Sun Microsystems, Incorporated. NFS: Network File System protocol specification, Technical report RFC--1094, March 1989.

....of users and hundreds of workstations. For the purpose to offer the same operational environment for all uses at all workstations, the users personal data or public data are often stored and managed at one or more file servers with distributed file systems (DFS) like Network File System (NFS)[5] or Andrew File System (AFS) 6] Of course the same environment can be stored locally on the users workstations. However it is difficult to manage local storage in hundreds of workstations and the cost of the storage would be expensive. When users use data in a file server of DFS, request ....

Sun Microsystems, Inc, "NFS: network file system protocol specification," RFC 1094, 1989

....and guaranteeing, at the same time, compatibility among all applications. Then, if the file system is a distributed file system, it becomes possible to grant file system access to any distributed application, thus enhancing data visibility. A file system such as the NFS (Network File System) Mic89] file system may be used. Since NFS is a standard and is included, by default, in most operating systems, its use becomes inexpensive and the overhead in terms of configuration and integration procedures is almost inexistent. Real time behavior of the NavCim platform is not a hard requirement. ....

Sun Microsystems. NFS: Network File System Protocol Specification. Technical Report RFC 1094, Sun Microsystems, Mountain View, CA., March 1989.

....peripherals from network attached peripherals. At the other end of the spectrum, it becomes difficult (and sometimes irrelevant) to distinguish NAPs from network hosts that provide certain services. The obvious example is a specialpurpose network node that provide NFS (Network File System)[58, 13] services only no generalpurpose computing facilities. Examples include the Parity Systems Etherstore[48] Auspex NS7000 3 , Network Appliance 4 [31] and the Maximum Strategy proFILE XL RAID array[1] However, the high level 3 http: www.auspex.com 4 http: www.netapp.com protocol ....

Sun Microsystems Inc. NFS: Network file system protocol specification, 1989.

....such as locking, audit trails, or restricting the accessible portion of a file. 3.2 Network File System (NFS) NFS is one of the oldest and most widely used network filesystem. Initially designed by Sun Microsystems in 1983, NFS was opened up to the public through an informational internet RFC [Sun89] and was implemented in the early Berkeley Unix systems. NFS provides a peer to peer file sharing mechanism where a server exports some or all of its storage to the world. Now, almost every Unix based platform ships with NFS support to import and export storage systems. Sun defined NFSv3, the ....

Sun Microsystems, Inc., NFS: Network File Systems Protocol Specification, Internet RFC 1094, March 1989.

....increase, and requires the assumption that multicast packets will not be dropped by routers. LegionFS supports location transparency through its three tiered namespace, rather than through multicast. Unified namespaces are well established in distributed file systems such as Sprite [Nel88] NFS[Sun88], and Locus [Wal83] and location independent naming schemes are used in AFS [How88] LegionFS provides a single, persistent namespace with location independent naming to facilitate file migration. The naming scheme is designed to be extensible, so that future requirements in naming can also be ....

Sun Microsystems, NFS: Network File System Protocol Specification, Request for Comments 1094, 1988.

....with the new implementation, which allows streaming. Despite these problems CLAN IP is able to deliver nearly 10 times the performance of gigabit ethernet for 1 kilobyte messages. 6. 2 NFS Another service which we have implemented in the Linux kernel is the Sun Network File System Protocol[20] (NFS) The implementation consists of two sets of modifications: # The SunRPC layer runs over a custom socket implementation over the CLAN NIC. # A number of DMA optimisations are added at higher levels in the NFS subsystem to increase performance for file data transfer. A CLAN connection is ....

Sun Microsystems. NFS: Network File System Protocol Specification, 1989. RFC 1050.

....can be mapped using Unix V shared memory, memory mapped files, or by reading the file into an anonymous memory mapped region. The memory mapped file mechanism is primarily intended to be used within a local area network since it can take advantage of existing distributed file systems (such as NFS [117]) Due to garbage collection, some segments in a bunch may become empty, i.e. with no reachable objects inside. In this case, the virtual memory space occupied by such a segment is freed to the corresponding CM. The CM adds that memory space to its list of free address space slices, for future ....

Sun Microsystems, Inc. NFS: Network file system protocol specification. RFC 1094, Network Information Center, SRI International, March 1989.

No context found.

Sun Microsystems, Inc., "NFS: Network File System Protocol Specification", RFC 1094, March 1989. http://www.ietf.org/rfc/rfc1094.txt

No context found.

Sun Microsystems, Inc., "NFS: Network File System Protocol Specification", RFC 1094, March 1989. http://www.ietf.org/rfc/rfc1094.txt

No context found.

Sun Microsystems, Inc., "NFS: Network File System Protocol Specification", RFC 1094, March 1989. http://www.ietf.org/rfc/rfc1094.txt

No context found.

Sun Microsystems, Inc., "NFS: Network File System Protocol Specification", RFC 1094, March 1989. http://www.ietf.org/rfc/rfc1094.txt

No context found.

Sun Microsystems, Inc., "NFS: Network File System Protocol Specification", RFC 1094, March 1989.

No context found.

Sun Microsystems. NFS: network file system protocol specification, RFC--1094, March 1989.

No context found.

Sun Microsystems, Inc. NFS: network file system protocol specification. RFC--1094. Network Working Group, March 1989.

No context found.

Sun Microsystems. NFS: network file system protocol specification, RFC--1094, March 1989.

No context found.

Sun Microsystems, "NFS: Network file system protocol specification", RFC 1094, Network Information Center, SRI International, March, 1989.

No context found.

Sun Microsystems, Inc. NFS: network file system protocol specification. RFC--1094. Network Working Group, March 1989.

No context found.

Sun Microsystems, Inc., "NFS: Network File System Protocol Specification," Internet RFC 1094, March 1989.

No context found.

Sun Microsystems. NFS: Network file system protocol specification. Technical Report RFC 1094, Network Working Group, March 1989.

No context found.

Sun Microsystems. NFS: Network file system protocol specification. Technical Report RFC 1094, Network Working Group, March 1989.

No context found.

Sun Microsystems. NFS: Network file system protocol specification. Technical Report RFC 1094, Network Working Group, March 1989.

No context found.

Sun Microsystems Inc. Nfs: Network file system protocol specification. Request for Comments (RFC) 1094, Network Working Group, March 1989.

No context found.

Sun Microsystems, "NFS: Network File System Protocol specification," RFC 1094, Mar. 1989.

No context found.

Microsystems, Sun., "NFS: Network File System Protocol specification", RFC 1094, March 1989.

No context found.

Sun Microsystems, "NFS: Network File System Protocol Specification." http://www.ietf.org/rfc/ rfc1057.txt, June 1988.

No context found.

Sun Microsystems. NFS: Network file system protocol specification. Network Working Group, Request for Comments (RFC 1094), March 1989. Version 2.

No context found.

Sun Microsystems, `NFS: network file system protocol specification', Technical Report RFC-1094, Internet Request For Comments(March 1989).

No context found.

Sun Microsystems, `NFS: network file system protocol specification', Technical Report RFC-1094, Internet Request For Comments (1989).

No context found.

Sun Microsystems. NFS: Network File System Protocol Specification, 1989. RFC 1050.

No context found.

Sun Microsystems, Inc. NFS: Network File System Protocol Specification. Available at http://www.cis.ohio-state.edu/htbin/rfc/rfc1094.html, 1989.

No context found.

Sun Microsystems. March 1989. NFS : Network File System Protocol Specification. RFC 1094. ftp://ftp.isi.edu/in-notes/rfc1094.txt

No context found.

Sun Microsystems, Inc. NFS: Network File System protocol Specification. RFC 1094, network Working Group, March 1989.

First 50 documents  Next 50

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