Lines Matching refs:FS

208   assists in locating the correct FS drivers.  Sometimes after extensive
209   pre-processing, the VFS starts invoking exported routines in the FS
210   driver.  This is the point where the FS specific processing of the
214   The FS layer for Coda must expose and implement several interfaces.
216   the Coda FS layer, so the Coda FS driver must expose the VFS interface
219   read/write and create and remove objects.  The Coda FS layer services
222   come back to the FS driver, servicing of the VFS call continues and
226   As a result of this design a basic interface exposed by the FS driver
238                      Interfaces of the Coda FS Driver
240   Furthermore the FS layer provides for a special path of communication
249   Finally Venus allows the kernel FS driver to cache the results from
254   to the Coda FS layer to request flushes or updates in the cache.  The
255   kernel FS driver handles such requests synchronously.
268   At the lowest level the communication between Venus and the FS driver
271   up processes.  The Coda FS driver processes VFS- and pioctl-requests
276   FS Driver in kernel memory on behalf of P and copied to user memory in
279   The FS Driver while servicing P makes upcalls to Venus.  Such an
303   Venus detects the notification that a message has arrived, and the FS
310   At some later point the FS driver receives a message from Venus,
311   namely when Venus calls sendmsg_to_kernel.  At this moment the Coda FS
317      WRITTEN.  Finally, the FS driver unblocks P (still in the kernel
324      the FS Driver. The FS driver processes the request immediately
333   deallocate the message structure and return.  The FS routine can proceed
380   This section describes the upcalls a Coda FS driver can make to Venus.
656   NNoottee Many kernel FS drivers (Linux, NT and Windows 95) need to acquire
690   The only attributes which the FS driver may request to change are the
766   attributes of the file are returned.  The Coda FS Driver will normally
1010   for Unix and Windows systems.  For Unix systems the Coda FS Driver is
1429   The Coda FS Driver can cache results of lookup and access upcalls, to
1432   information is that Venus will notify the FS Driver that cached
1453   The lookup call in the Coda FS Driver may request the cnode of the
1456   that it cannot be found.  The Coda FS Driver must be careful to
1461   intercepted by the Coda FS Driver and lead to cache invalidations of
1462   the kind described below.  The Coda FS Driver does not return an error
1599   FS Driver at startup and upon shutdown or Venus failures.  Before
1600   entering the discussion it is useful to repeat that the Coda FS Driver