Lines Matching +full:read +full:- +full:out
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
143 are ``read``, ``write``, ``open``, ``close``, ``create``, ``mkdir``,
153 pre-processing, the VFS starts invoking exported routines in the FS
163 read/write and create and remove objects. The Coda FS layer services
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
243 queue of processing messages and setting flags to READ. Venus is
277 at the flags field. If the message is not yet READ, the process P can
278 handle its signal without notifying Venus. If Venus has READ, and
281 signals are put in the queue at the head, and read first by Venus. If
283 processing. The VFS routine will now continue. (-- If a VFS request
286 to indicate points of no return have been passed.--)
291 ----------------------------
295 retrieves messages by doing a read on the device, replies are sent
334 <union "out" of call dependent parts of inputArgs>
354 ----------------------------------------------------
432 --------------------------
458 caddr_t in, out; /* Data to be transferred in, or out */
475 ----------
483 out::
494 contains the ViceFid of the root of the Coda filesystem. If a non-zero
500 ------------
516 out::
549 -------------
564 out::
593 -------------
610 out
616 in BSD style. Attributes not to be changed are set to -1, apart from
628 ------------
641 out
659 ------------
679 out::
715 (2) to return a file descriptor for READ or WRITE mode.
722 -----------
739 out::
768 -----------
785 out
801 --------------
819 out
836 -------------
852 out
868 ------------
884 out
897 ---------------
901 Read the value of a symbolic link.
912 out::
931 -----------
947 out::
975 ------------
991 out
1012 ------------
1031 out::
1053 -------------
1071 out
1083 --------------
1087 Read directory entries.
1101 out::
1111 Read directory entries from VFid starting at offset and
1112 read at most count bytes. Returns the data in data and returns
1119 files. We will re-evaluate this during the directory revamp which is
1124 -----------
1128 instructs Venus to do an FSDB->Get.
1139 out::
1155 since it can be used to deal with read/write memory mapped files.
1161 ------------
1176 out
1189 ---------------
1204 out
1215 -----------
1219 Read or write from a file
1236 out::
1247 This upcall asks Venus to read or write from a file.
1253 read/write operations never reach Venus. I have been told the
1259 ---------------
1274 out::
1294 -----------------
1306 out
1315 -----------------
1326 out
1334 ---------------
1346 out
1361 -------------
1372 out
1377 This is an out-of-band upcall to Venus to inform Venus
1378 that the calling process received a signal after Venus read the
1433 unless the downcall data could not be read into kernel memory.
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.
1649 read/write, readdir) can proceed without upcalls. These must be