Lines Matching +full:no +full:- +full:can +full:- +full:fd

19 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
35 may occur in a non-blocking or asynchronous fashion are
36 common to all system-defined abstractions and are described here.
40 The \fIread\fP and \fIwrite\fP system calls can be applied
44 cc = read(fd, buf, nbytes);
45 result int cc; int fd; result caddr_t buf; int nbytes;
47 cc = write(fd, buf, nbytes);
48 result int cc; int fd; caddr_t buf; int nbytes;
51 object defined by \fIfd\fP to the buffer at address \fIbuf\fP of
53 returned in \fIcc\fP, which is \-1 if a return occurred before
54 any data was transferred because of an error or use of non-blocking
58 object defined by \fIfd\fP.  Depending on the type of \fIfd\fP,
77 cc = readv(fd, iov, iovlen);
78 result int cc; int fd; struct iovec *iov; int iovlen;
80 cc = writev(fd, iov, iovlen);
81 result int cc; int fd; struct iovec *iov; int iovlen;
90 ioctl(fd, request, buffer);
91 int fd, request; caddr_t buffer;
94 on the object \fIfd\fP.  The \fIrequest\fP parameter specifies
107 Non-blocking and asynchronous operations
109 A process that wishes to do non-blocking operations on one of
110 its descriptors sets the descriptor in non-blocking mode as
112 return a specific EWOULDBLOCK error indication if there is no data to be
117 Output attempted when a descriptor can accept less than is requested
120 More output can be performed as soon as a \fIselect\fP call indicates
124 may be performed on a descriptor in a non-blocking fashion.