Lines Matching +full:role +full:- +full:switch +full:- +full:default +full:- +full:mode
1 .. SPDX-License-Identifier: GPL-2.0
4 Coda Kernel-Venus Interface
10 Coda -- this document describes the client kernel-Venus interface.
35 level filesystem code needed for the operation of the Coda file sys-
124 leads to an almost natural environment for implementing a kernel-level
153 pre-processing, the VFS starts invoking exported routines in the FS
208 up processes. The Coda FS driver processes VFS- and pioctl-requests
220 memory for the request. Since the data buffer is re-used to hold the
234 in upcall. The (kernel mode) processing of P in the filesystem
255 mode context of Venus) and the sendmsg_to_kernel call returns to
283 processing. The VFS routine will now continue. (-- If a VFS request
286 to indicate points of no return have been passed.--)
291 ----------------------------
339 Before going on let us elucidate the role of the various fields. The
354 ----------------------------------------------------
375 default uid/gid. Perhaps the list of group membership is superfluous.
390 for a detailed description of the role of the SCM.
410 u_short va_mode; /* files access mode and type */
432 --------------------------
475 ----------
494 contains the ViceFid of the root of the Coda filesystem. If a non-zero
500 ------------
549 -------------
593 -------------
616 in BSD style. Attributes not to be changed are set to -1, apart from
619 mode, owner, groupid, atime, mtime and ctime. The return value
628 ------------
659 ------------
672 int mode;
691 will be name, and the mode will be mode. If excl is set an error will
713 together with the mode, could simply be part of the mode as it is
715 (2) to return a file descriptor for READ or WRITE mode.
722 -----------
751 Only the mode field in the input parameters is used for creation.
760 The input parameter should be changed to mode instead of
768 -----------
801 --------------
836 -------------
868 ------------
897 ---------------
931 -----------
975 ------------
1012 ------------
1053 -------------
1083 --------------
1119 files. We will re-evaluate this during the directory revamp which is
1124 -----------
1128 instructs Venus to do an FSDB->Get.
1161 ------------
1189 ---------------
1215 -----------
1259 ---------------
1294 -----------------
1315 -----------------
1334 ---------------
1361 -------------
1377 This is an out-of-band upcall to Venus to inform Venus
1401 context switch needs to take place. The counterpart of caching the
1437 ----------------
1444 -----------
1462 ---------------
1468 struct cfs_purgeuser_out {/* CFS_PURGEUSER is a venus->kernel call */
1480 -------------
1486 struct cfs_zapfile_out { /* CFS_ZAPFILE is a venus->kernel call */
1506 ------------
1512 struct cfs_zapdir_out { /* CFS_ZAPDIR is a venus->kernel call */
1525 --------------
1532 struct cfs_zapvnode_out { /* CFS_ZAPVNODE is a venus->kernel call */
1545 --------------
1551 struct cfs_purgefid_out { /* CFS_PURGEFID is a venus->kernel call */
1565 -------------
1574 struct cfs_replace_out { /* cfs_replace is a venus->kernel call */
1623 ------------------
1631 - Before opening, no messages can be placed.
1633 - Opening will remove any old messages still pending.
1635 - Close will notify any sleeping processes that their upcall cannot
1638 - Close will free all memory allocated by the message queues.