Searched refs:one (Results 1 – 25 of 27) sorted by relevance
12
| /libuv/src/win/ |
| H A D | atomicops-inl.h | 47 const char one = 1; in uv__atomic_exchange_set() local
51 : "0"(one), "m"(*target) in uv__atomic_exchange_set()
|
| /libuv/docs/src/guide/ |
| H A D | eventloops.rst | 35 ``uv_stop()`` in one of the check handlers, I/O has already finished and is not
39 there is an error, without having to ensure that all handlers are stopped one
40 by one.
|
| H A D | processes.rst | 8 A common idiom in Unix is for every process to do one thing and do it well. In
11 may also be easier to reason about compared to one with threads and shared
17 cores, improving performance. But an event loop has only one thread. The
48 one larger than the number of arguments, with the last element being NULL**.
122 libuv wraps the standard ``kill(2)`` system call on Unix and implements one
123 with similar semantics on Windows, with *one caveat*: all of ``SIGTERM``,
143 can only be associated with one signal number, with subsequent calls to
156 in that it will process only one event. UV_RUN_ONCE blocks if there are no
158 so that one of the loops isn't starved because the other one has no pending
162 4 times, one for each ``uv_signal_t``. The handler just stops each handle,
[all …]
|
| H A D | about.rst | 4 `Nikhil Marathe <https://nikhilism.com>`_ started writing this book one
|
| H A D | basics.rst | 55 data. It is **asynchronous** because the application expressed interest at one
69 Bert Belder, one of the libuv core developers has a small video explaining the
191 only one callback) and usually indicates one I/O operation on a handle.
|
| H A D | threads.rst | 28 This chapter makes the following assumption: **There is only one event loop,
29 running in one thread (the main thread)**. No other thread interacts
153 pointer, **only the first one will win, the function will be called once and
202 want responsiveness (the classic 'one thread per client' server model), and
324 ``uv_async_send``. Your callback will never be called twice for just one
|
| H A D | filesystem.rst | 80 one-off, or are done as part of the startup or shutdown stage are performed
283 file change notification libraries [#fsnotify]_. This is one of the more
332 #. ``int events`` - one of ``UV_RENAME`` or ``UV_CHANGE``, or a bitwise OR of
|
| H A D | utilities.rst | 141 This allows cleaning up the work request and all the data in one free call.
|
| /libuv/docs/src/ |
| H A D | poll.rst | 101 with one of the `UV_E*` error codes (see :ref:`errors`). The user should
117 If one of the events `UV_READABLE` or `UV_WRITABLE` are set, the
|
| H A D | threading.rst | 166 same guard will block all callers except one (it's unspecified which one).
|
| H A D | migration_010_100.rst | 241 In addition, instead of allocating a full list strings, the user is able to get one
|
| H A D | tcp.rst | 86 from the previous one, will still happen. If the connection is still lost
|
| H A D | udp.rst | 43 * they all set the flag) but only the last one to bind will receive
168 The remaining bits can be used to set one of these flags:
|
| H A D | loop.rst | 160 poll in one thread and run the event loop's callbacks in another see
|
| H A D | fs.rst | 607 `O_CREAT`. There is one exception: on Linux 2.6 and later, `O_EXCL` can
640 process does not already have one).
|
| H A D | misc.rst | 790 On Windows, the returned priority will equal one of the `UV_PRIORITY`
806 process priority, the result will equal one of the `UV_PRIORITY`
|
| /libuv/ |
| H A D | README.md | 171 **Required Components:** "MSbuild", "VC++ 2017 v141 toolset" and one of the
223 "ARCHS" flag. You can specify more than one by delimiting with a space
256 #### Run one test
|
| H A D | CONTRIBUTING.md | 97 changed and why. Follow these guidelines when writing one:
108 subsystem: explaining the commit in one line
|
| H A D | SUPPORTED_PLATFORMS.md | 50 supported, but if one of the two does not support the new platform it can be
|
| H A D | .mailmap | 54 TK-one <tk5641@naver.com>
|
| H A D | LICENSE-docs | 38 Considerations for the public: By using one of our public
379 licenses. Notwithstanding, Creative Commons may elect to apply one of
|
| H A D | AUTHORS | 418 TK-one <tk5641@naver.com>
|
| /libuv/docs/ |
| H A D | Makefile | 27 @echo "Please use \`make <target>' where <target> is one of"
|
| H A D | make.bat | 21 echo.Please use `make ^<target^>` where ^<target^> is one of
|
| /libuv/m4/ |
| H A D | ax_pthread.m4 | 123 # (e.g. DEC) have both -lpthread and -lpthreads, where one of the
292 # links in two steps (.c -> .o, .o -> exe) instead of one
366 # pthread_cleanup_push because it is one of the few pthread
|
Completed in 53 milliseconds
12
