Lines Matching refs:VFS
177 VFS interface. Similar functionality is provided, and the format of
178 the parameters and returned data is very similar to the BSD VFS. This
204 filesystem (VFS) layer, which is named I/O Manager in NT and IFS
205 manager in Windows 95. The VFS is responsible for partial processing
209 pre-processing, the VFS starts invoking exported routines in the FS
215 First and foremost the VFS must be able to make all necessary calls to
216 the Coda FS layer, so the Coda FS driver must expose the VFS interface
220 such VFS requests by invoking one or more well defined services
222 come back to the FS driver, servicing of the VFS call continues and
223 finishes with a reply to the kernel's VFS. Finally the VFS layer
257 Among these interfaces the VFS interface and the facility to place,
259 not go into the calls exported to the VFS layer but we will state the
271 up processes. The Coda FS driver processes VFS- and pioctl-requests
351 processing. The VFS routine will now continue. (-- If a VFS request
776 indicate confusion between the system call creat and the VFS operation
777 create. The VFS operation create is only called to create new objects.
1329 removed since it causes a jungle of pointers in the VFS mounting area.
1620 2. the VFS layer
1624 Currently the _p_i_o_c_t_l passes through the VFS for Coda so we can
1648 3. Before the message queues are open, all VFS operations will fail.
1652 4. After closing of the queues, no VFS operations can succeed. Here