Lines Matching full:coda
4 Coda Kernel-Venus Interface
10 Coda -- this document describes the client kernel-Venus interface.
14 http://www.coda.cs.cmu.edu
16 For user level software needed to run Coda:
18 ftp://ftp.coda.cs.cmu.edu
20 To run Coda you need to get a user level cache manager for the client,
22 client needs to have the Coda filesystem selected in the kernel
35 level filesystem code needed for the operation of the Coda file sys-
43 2. Servicing Coda filesystem calls
98 A key component in the Coda Distributed File System is the cache
101 When processes on a Coda enabled system access files in the Coda
105 client cache and makes remote procedure calls to Coda file servers and
110 kernel support for Coda may maintain a minicache of recently processed
120 Historically Coda was implemented in a BSD file system in Mach 2.6.
125 filesystem driver for Coda in a BSD system. However, other operating
129 To implement Coda on these systems some reverse engineering of the
137 2. Servicing Coda filesystem calls
140 The service of a request for a Coda file system service originates in
141 a process P which accessing a Coda file. It makes a system call which
155 request starts, and here the Coda specific kernel code comes into
158 The FS layer for Coda must expose and implement several interfaces.
160 the Coda FS layer, so the Coda FS driver must expose the VFS interface
163 read/write and create and remove objects. The Coda FS layer services
177 **Interfaces of the Coda FS Driver**
181 pioctl interface is used for Coda specific services, such as
193 to the Coda FS layer to request flushes or updates in the cache. The
207 requesting Coda file service and Venus relies on blocking and waking
208 up processes. The Coda FS driver processes VFS- and pioctl-requests
248 namely when Venus calls sendmsg_to_kernel. At this moment the Coda FS
294 implementation of a character device associated with Coda. Venus
313 This section describes the upcalls a Coda FS driver can make to Venus.
361 semantics for Coda but the structure may have to undergo modification
378 The next item is the fundamental identifier used to identify Coda
380 directory in the Coda filesystem within a cell [1]_::
388 .. [1] A cell is agroup of Coda servers acting under the aegis of a single
389 system control machine or SCM. See the Coda Administration manual
394 to be prefixed to identify the Coda cell; this will probably take the
395 form of a Ipv6 size IP address naming the Coda cell through DNS.
400 support for device files (currently not present in Coda)::
435 Coda specific requests can be made by application through the pioctl
437 fictitious file /coda/.CONTROL. The pioctl call opens this file, gets
442 the pioctl data buffers is a file in a Coda filesystem.
465 The path must be a Coda file, otherwise the ioctl upcall will not be
493 the Coda filesystem. If the result is zero, the cfs_root structure
494 contains the ViceFid of the root of the Coda filesystem. If a non-zero
497 the Coda filesystem.
648 access will be granted. It is important to remember that Coda uses
696 attributes of the file are returned. The Coda FS Driver will normally
792 target's parent, i.e. the source must be have parent destFid, i.e. Coda
960 for Unix and Windows systems. For Unix systems the Coda FS Driver is
1252 It should be removed since it is against the Coda philosophy that
1263 Allows mounting multiple Coda "filesystems" on one Unix mount point.
1283 Asks Venus to return the rootfid of a Coda system named
1290 It is not used by Coda proper. Call is not implemented by Venus.
1356 .. Note:: Gut it. It isn't working and isn't used by Coda.
1399 The Coda FS Driver can cache results of lookup and access upcalls, to
1423 The lookup call in the Coda FS Driver may request the cnode of the
1426 that it cannot be found. The Coda FS Driver must be careful to
1431 intercepted by the Coda FS Driver and lead to cache invalidations of
1432 the kind described below. The Coda FS Driver does not return an error
1592 This section gives brief hints as to desirable features for the Coda
1594 entering the discussion it is useful to repeat that the Coda FS Driver
1607 much more delicate. User processes hold reference counts in Coda
1618 Currently the pioctl passes through the VFS for Coda so we can
1645 Coda filesystem cannot succeed before opening.
1658 8. Mounting the Coda filesystem should fail gracefully if Venus cannot