Lines Matching refs:FS
152 assists in locating the correct FS drivers. Sometimes after extensive
153 pre-processing, the VFS starts invoking exported routines in the FS
154 driver. This is the point where the FS specific processing of the
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
166 come back to the FS driver, servicing of the VFS call continues and
170 As a result of this design a basic interface exposed by the FS driver
177 **Interfaces of the Coda FS Driver**
179 Furthermore the FS layer provides for a special path of communication
188 Finally Venus allows the kernel FS driver to cache the results from
193 to the Coda FS layer to request flushes or updates in the cache. The
194 kernel FS driver handles such requests synchronously.
205 At the lowest level the communication between Venus and the FS driver
208 up processes. The Coda FS driver processes VFS- and pioctl-requests
213 FS Driver in kernel memory on behalf of P and copied to user memory in
216 The FS Driver while servicing P makes upcalls to Venus. Such an
240 Venus detects the notification that a message has arrived, and the FS
247 At some later point the FS driver receives a message from Venus,
248 namely when Venus calls sendmsg_to_kernel. At this moment the Coda FS
254 WRITTEN. Finally, the FS driver unblocks P (still in the kernel
261 the FS Driver. The FS driver processes the request immediately
270 deallocate the message structure and return. The FS routine can proceed
313 This section describes the upcalls a Coda FS driver can make to Venus.
582 Many kernel FS drivers (Linux, NT and Windows 95) need to acquire
618 The only attributes which the FS driver may request to change are the
696 attributes of the file are returned. The Coda FS Driver will normally
960 for Unix and Windows systems. For Unix systems the Coda FS Driver is
1399 The Coda FS Driver can cache results of lookup and access upcalls, to
1402 information is that Venus will notify the FS Driver that cached
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
1593 FS Driver at startup and upon shutdown or Venus failures. Before
1594 entering the discussion it is useful to repeat that the Coda FS Driver