Lines Matching full:call

49   4. The interface at the call level
141   a process P which accessing a Coda file. It makes a system call which
166   come back to the FS driver, servicing of the VFS call continues and
242   call. This action finishes in the kernel by putting the message on the
244   passed the contents of the data buffer. The getmsg_from_kernel call
255      mode context of Venus) and the sendmsg_to_kernel call returns to
269   sendmsg_to_kernel call.  In the normal case, the upcall routine will
296   with a write and notification is through the select system call on the
301   call is used.  The DeviceIoControl call is designed to copy buffers
303   is issued as a synchronous call, while the getmsg_from_kernel call is
309 4.  The interface at the call level
326 	    <union "in" of call dependent parts of inputArgs>
334 	    <union "out" of call dependent parts of inputArgs>
437   fictitious file /coda/.CONTROL.  The pioctl call opens this file, gets
438   a file handle and makes the ioctl call. Finally it closes the file.
492     This call is made to Venus during the initialization of
526     This call is made to determine the ViceFid and filetype of
573     This call returns the attributes of the file identified by fid.
650     clients enforce the security of the system.  The result of this call
709      indicate confusion between the system call creat and the VFS operation
711      This create call differs from the Unix one in that it is not invoked
750     This call is similar to create but creates a directory.
790     This call creates a link to the sourceFid in the directory
1118      This call is not used.  Readdir operations exploit container
1185   .. Note:: Linux does not implement this call. It should.
1288      This call was used by David for dynamic sets.  It should be
1290      It is not used by Coda proper.  Call is not implemented by Venus.
1311   .. Note:: Gut it. Call is not implemented by Venus.
1330   .. Note:: Gut it. Call is not implemented by Venus.
1351     Venus worker.cc has support for this call, although it is
1389      per system call situations correctly.  It would be important to know
1423   The lookup call in the Coda FS Driver may request the cnode of the
1440   No information is available on this call.
1455     Venus issues this call upon startup and when it dies. This
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.
1486 	  struct cfs_zapfile_out {  /* CFS_ZAPFILE is a venus->kernel call */
1499      Call is not named correctly in NetBSD and Mach.  The minicache
1512 	  struct cfs_zapdir_out {   /* CFS_ZAPDIR is a venus->kernel call */
1520     CodaFid, and all children of this directory. This call is issued when
1532 	  struct cfs_zapvnode_out { /* CFS_ZAPVNODE is a venus->kernel call */
1551 	  struct cfs_purgefid_out { /* CFS_PURGEFID is a venus->kernel call */
1574 	  struct cfs_replace_out { /* cfs_replace is a venus->kernel call */