Lines Matching +full:len +full:- +full:or +full:- +full:limit
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-
111 requests to limit the number of interactions with Venus. Venus
124 leads to an almost natural environment for implementing a kernel-level
153 pre-processing, the VFS starts invoking exported routines in the FS
164 such VFS requests by invoking one or more well defined services
175 when no messages are waiting or being processed.
192 information must be flushed or replaced. Venus then makes a downcall
193 to the Coda FS layer to request flushes or updates in the cache. The
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
262 (usually a cache eviction or replacement) and when it finishes
268 attempt to terminate P) or as is normally the case by Venus in its
283 processing. The VFS routine will now continue. (-- If a VFS request
286 to indicate points of no return have been passed.--)
291 ----------------------------
354 ----------------------------------------------------
379 files, the ViceFid. A fid of a file uniquely defines a file or
389 system control machine or SCM. See the Coda Administration manual
432 --------------------------
458 caddr_t in, out; /* Data to be transferred in, or out */
475 ----------
494 contains the ViceFid of the root of the Coda filesystem. If a non-zero
500 ------------
529 The result may indicate that the name does not exist, or that
549 -------------
577 unaccessible or if the caller does not have permission to fetch
584 "inode" or "FileHandle". A significant improvement in performance on
593 -------------
616 in BSD style. Attributes not to be changed are set to -1, apart from
620 indicates success or failure.
624 be inaccessible, or permission may not be granted by Venus.
628 ------------
654 The object may not exist, or the ACL describing the protection
659 ------------
697 instantiate a vnode, inode or file handle at kernel level for the new
715 (2) to return a file descriptor for READ or WRITE mode.
722 -----------
768 -----------
794 relevant. It indicates success or the type of failure.
801 --------------
836 -------------
868 ------------
897 ---------------
924 to hold any name up to CFS_MAXNAMLEN (PATH or NAM??).
931 -----------
975 ------------
1012 ------------
1024 int len;
1035 int len;
1042 Do an ioctl operation on a file. The command, len and
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 -----------
1219 Read or write from a file
1247 This upcall asks Venus to read or write from a file.
1259 ---------------
1294 -----------------
1315 -----------------
1334 ---------------
1361 -------------
1377 This is an out-of-band upcall to Venus to inform Venus
1400 limit the frequency of upcalls. Upcalls carry a price since a process
1403 entries must be flushed or renamed.
1425 CodaCred's of the caller. The cache will return the cnode or indicate
1427 invalidate cache entries when it modifies or removes objects.
1437 ----------------
1444 -----------
1462 ---------------
1468 struct cfs_purgeuser_out {/* CFS_PURGEUSER is a venus->kernel call */
1476 call is issued when tokens for a user expire or are flushed.
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 */
1593 FS Driver at startup and upon shutdown or Venus failures. Before
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.
1659 get the rootfid or the attributes of the rootfid. The latter is