Home
last modified time | relevance | path

Searched refs:operation (Results 1 – 11 of 11) sorted by relevance

/libuv/src/win/
H A Dwinsock.h139 #define _AFD_CONTROL_CODE(operation, method) \ argument
140 ((FSCTL_AFD_BASE) << 12 | (operation << 2) | method)
/libuv/docs/src/
H A Derrors.rst116 operation canceled
172 illegal operation on a directory
248 socket operation on non-socket
252 operation not supported on socket
260 operation not permitted
H A Dpipe.rst72 for unsupported flags without performing the bind operation.
102 for unsupported flags without performing the connect operation.
H A Ddesign.rst53 (readable, writable hangup) so handles can read, write or perform the desired I/O operation.
95 for a read or write operation get their callbacks called at this point.
H A Dprocess.rst121 * the operation to perform for the corresponding file descriptor
H A Dstream.rst235 operation will still be reported through a callback which is made
H A Dloop.rst80 This operation is currently only implemented for SIGPROF signals,
H A Dhandle.rst13 functions must remain valid for the duration of the requested operation. Take
H A Dfs.rst248 crash if the memory mapped read operation fails.
262 crash if the memory mapped write operation fails.
/libuv/docs/src/guide/
H A Dbasics.rst43 One of the standard solutions is to use threads. Each blocking I/O operation is
191 only one callback) and usually indicates one I/O operation on a handle.
H A Dfilesystem.rst46 Filesystem operation callbacks have the signature:

Completed in 18 milliseconds