Searched refs:I (Results 1 – 22 of 22) sorted by relevance
| /libuv/docs/src/ |
| H A D | design.rst | 8 around the event-driven asynchronous I/O model.
40 The I/O loop
43 The I/O (or event) loop is the central part of libuv. It establishes the content for all I/O
72 #. Pending callbacks are called. All I/O callbacks are called right after polling for I/O, for the
80 the loop will block for I/O.
93 #. The loop blocks for I/O. At this point the loop will block for I/O for the duration calculated
116 network I/O is **always** performed in a single thread, each loop's thread.
123 File I/O
126 Unlike network I/O, there are no platform-specific file I/O primitives libuv could rely on,
127 so the current approach is to run blocking file I/O operations in a thread pool.
[all …]
|
| H A D | index.rst | 8 libuv is a multi-platform support library with a focus on asynchronous I/O. It
|
| H A D | tty.rst | 32 /* Binary-safe I/O mode for IPC (Unix-only) */
|
| H A D | pipe.rst | 176 or `FIONBIO`/`O_NONBLOCK` I/O usage.
|
| H A D | fs.rst | 576 File I/O is done directly to and from user-space buffers, which must be
594 The file is opened for synchronous I/O. Write operations will complete once
699 The file is opened for synchronous I/O. Write operations will complete once
|
| H A D | tcp.rst | 184 or `FIONBIO`/`O_NONBLOCK` I/O usage.
|
| H A D | misc.rst | 287 still event loops or I/O requests active.
688 [--I] signal 0x1a25ea8
697 - `I` is printed for a handle that is internal
|
| /libuv/ |
| H A D | libuv-static.pc.in | 8 Description: multi-platform support library with a focus on asynchronous I/O.
12 Cflags: -I${includedir}
|
| H A D | libuv.pc.in | 9 Description: multi-platform support library with a focus on asynchronous I/O.
13 Cflags: -I${includedir}
|
| H A D | SUPPORTED_PLATFORMS.md | 37 I/O handling is abstracted by an internal `uv__io_t` handle. The new platform
|
| H A D | README.md | 5 libuv is a multi-platform support library with a focus on asynchronous I/O. It
|
| H A D | AUTHORS | 56 Iñaki Baz Castillo <ibc@aliax.net>
|
| H A D | ChangeLog | 4554 * tty: implement binary I/O terminal mode (Yuri D'Elia)
4981 * include: avoid using C++ 'template' reserved word (Iñaki Baz Castillo)
|
| /libuv/docs/src/guide/ |
| H A D | eventloops.rst | 31 runs pending timer, idle and prepare callbacks, and invokes any pending I/O
34 why the loop does not block on I/O. If on the other hand, you called
35 ``uv_stop()`` in one of the check handlers, I/O has already finished and is not
|
| H A D | introduction.rst | 5 a high performance evented I/O library which offers the same API on Windows and Unix.
14 I hope you will enjoy it as it grows.
38 combined a model of I/O -- evented -- with a language that was well suited to
|
| H A D | basics.rst | 5 core job is to provide an event loop and callback based notifications of I/O
41 as other activities and other I/O operations are kept waiting.
43 One of the standard solutions is to use threads. Each blocking I/O operation is
64 How the I/O is run in the background is not of our concern, but due to the
134 I/O read callbacks (such as for files and sockets) are passed a parameter ``nread``. If ``nread`` i…
140 usually done by creating a **handle** to an I/O device, timer or process.
191 only one callback) and usually indicates one I/O operation on a handle.
|
| H A D | utilities.rst | 191 External I/O with polling
194 Usually third-party libraries will handle their own I/O, and keep track of
196 the standard stream I/O operations, but the library can still be integrated
201 will perform the entire I/O transaction and only then return. It is unwise to
206 operating system notification mechanism. In some sense, all the I/O operations
214 progress with the download whenever libuv notifies of I/O readiness.
230 interval, after which we should drive libcurl forward regardless of I/O status.
375 implement the ANSI escape codes across all platforms. By this I mean that libuv
445 .. [#] I was first introduced to the term baton in this context, in Konstantin
|
| H A D | filesystem.rst | 81 synchronously, since we are interested in fast I/O when the program is going
82 about its primary task and dealing with multiple I/O sources*. For solo tasks
171 The basic I/O handle in libuv is the stream (``uv_stream_t``). TCP sockets, UDP
172 sockets, and pipes for file I/O and IPC are all treated as stream subclasses.
200 asynchronously shows the power of evented I/O. The two writes won't block each
286 difficult. To demonstrate, I'm going to build a simple utility which runs
|
| H A D | threads.rst | 71 This section is purposely spartan. This book is not about threads, so I only
197 when performing I/O or is a serious CPU hog*, because this means that the loop
201 a routine which performs I/O under the hood) to be used with threads if you
|
| H A D | processes.rst | 168 Child Process I/O
220 parent process, the child process can treat that stream as standard I/O. This
332 to hand off their I/O to other processes. Applications include load-balancing
|
| H A D | networking.rst | 10 The ``uv_tcp_t`` and ``uv_udp_t`` structures are used for network I/O.
|
| /libuv/test/ |
| H A D | test-tty-duplicate-key.c | 82 # define KEV(I) records[(I)].Event.KeyEvent in make_key_event_records() argument
|
Completed in 104 milliseconds
