Lines Matching refs:VFS
122 VFS interface. Similar functionality is provided, and the format of
123 the parameters and returned data is very similar to the BSD VFS. This
148 filesystem (VFS) layer, which is named I/O Manager in NT and IFS
149 manager in Windows 95. The VFS is responsible for partial processing
153 pre-processing, the VFS starts invoking exported routines in the FS
159 First and foremost the VFS must be able to make all necessary calls to
160 the Coda FS layer, so the Coda FS driver must expose the VFS interface
164 such VFS requests by invoking one or more well defined services
166 come back to the FS driver, servicing of the VFS call continues and
167 finishes with a reply to the kernel's VFS. Finally the VFS layer
196 Among these interfaces the VFS interface and the facility to place,
198 not go into the calls exported to the VFS layer but we will state the
208 up processes. The Coda FS driver processes VFS- and pioctl-requests
283 processing. The VFS routine will now continue. (-- If a VFS request
709 indicate confusion between the system call creat and the VFS operation
710 create. The VFS operation create is only called to create new objects.
1289 removed since it causes a jungle of pointers in the VFS mounting area.
1614 2. the VFS layer
1618 Currently the pioctl passes through the VFS for Coda so we can
1643 3. Before the message queues are open, all VFS operations will fail.
1647 4. After closing of the queues, no VFS operations can succeed. Here