Deleted Added
full compact
fsinterface.ms (1639) fsinterface.ms (18715)
1.\" Copyright (c) 1986 The Regents of the University of California.
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.

--- 16 unchanged lines hidden (view full) ---

25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" @(#)fsinterface.ms 1.4 (Berkeley) 4/16/91
1.\" Copyright (c) 1986 The Regents of the University of California.
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.

--- 16 unchanged lines hidden (view full) ---

25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" @(#)fsinterface.ms 1.4 (Berkeley) 4/16/91
33.\" $Id$
33.\"
34.if \nv .rm CM
35.de UX
36.ie \\n(UX \s-1UNIX\s0\\$1
37.el \{\
38\s-1UNIX\s0\\$1\(dg
39.FS
40\(dg \s-1UNIX\s0 is a registered trademark of AT&T.

--- 204 unchanged lines hidden (view full) ---

245\fINamei\fP performs name translation by iterative lookup
246of each component name in its directory to find its inumber,
247then using \fIiget\fP to return the actual inode.
248If the last component has been reached, this inode is returned;
249otherwise, the inode describes the next directory to be searched.
250The inode returned may be used in various ways by the caller;
251it may be examined, the file may be read or written,
252types and access may be checked, and fields may be modified.
34.\"
35.if \nv .rm CM
36.de UX
37.ie \\n(UX \s-1UNIX\s0\\$1
38.el \{\
39\s-1UNIX\s0\\$1\(dg
40.FS
41\(dg \s-1UNIX\s0 is a registered trademark of AT&T.

--- 204 unchanged lines hidden (view full) ---

246\fINamei\fP performs name translation by iterative lookup
247of each component name in its directory to find its inumber,
248then using \fIiget\fP to return the actual inode.
249If the last component has been reached, this inode is returned;
250otherwise, the inode describes the next directory to be searched.
251The inode returned may be used in various ways by the caller;
252it may be examined, the file may be read or written,
253types and access may be checked, and fields may be modified.
253Modified inodes are automatically written back the the filesystem
254Modified inodes are automatically written back the filesystem
254on disk when the last reference is released with \fIiput\fP.
255Although the details are considerably different,
256the same general scheme is used in the faster filesystem in 4.2BSD
257.UX
258[Mckusick85].
259.PP
260Both the AT&T interface and, to a lesser extent, the DEC interface
261attempt to preserve the inode-oriented interface.

--- 311 unchanged lines hidden (view full) ---

573This calling interface has the additional advantage
574that the call parameters need not all be pushed onto the stack for each call
575through the filesystem interface,
576and they may be accessed using short offsets from a base pointer
577(unlike global variables in the \fIuser\fP structure).
578.PP
579The proposed filesystem interface is described very tersely here.
580For the most part, data structures and procedures are analogous
255on disk when the last reference is released with \fIiput\fP.
256Although the details are considerably different,
257the same general scheme is used in the faster filesystem in 4.2BSD
258.UX
259[Mckusick85].
260.PP
261Both the AT&T interface and, to a lesser extent, the DEC interface
262attempt to preserve the inode-oriented interface.

--- 311 unchanged lines hidden (view full) ---

574This calling interface has the additional advantage
575that the call parameters need not all be pushed onto the stack for each call
576through the filesystem interface,
577and they may be accessed using short offsets from a base pointer
578(unlike global variables in the \fIuser\fP structure).
579.PP
580The proposed filesystem interface is described very tersely here.
581For the most part, data structures and procedures are analogous
581to those used by VFS, and only the changes will be be treated here.
582to those used by VFS, and only the changes will be treated here.
582See [Kleiman86] for complete descriptions of the vfs and vnode operations
583in Sun's interface.
584.PP
585The central data structure for name translation is the \fInameidata\fP
586structure.
587The same structure is used to pass parameters to \fInamei\fP,
588to pass these same parameters to filesystem-specific lookup routines,
589to communicate completion status from the lookup routines back to \fInamei\fP,

--- 587 unchanged lines hidden ---
583See [Kleiman86] for complete descriptions of the vfs and vnode operations
584in Sun's interface.
585.PP
586The central data structure for name translation is the \fInameidata\fP
587structure.
588The same structure is used to pass parameters to \fInamei\fP,
589to pass these same parameters to filesystem-specific lookup routines,
590to communicate completion status from the lookup routines back to \fInamei\fP,

--- 587 unchanged lines hidden ---