Searched refs:running (Results 1 – 14 of 14) sorted by relevance
| /libuv/test/ |
| H A D | benchmark-async-pummel.c | 34 static const char running[] = "running"; variable
56 while (ACCESS_ONCE(const char*, handle->data) == running) in pummel()
75 ACCESS_ONCE(const char*, handle.data) = running; in test_async_pummel()
|
| /libuv/docs/src/guide/ |
| H A D | threads.rst | 22 :ref:`first example <thread-create-example>`, don't even require a running
29 running in one thread (the main thread)**. No other thread interacts
204 own system of running the task in a separate thread. libuv just provides
222 you are changing things while both threads may be running.
235 will be called on the thread the event loop is running in. It will be passed
286 A well designed program would have a way to terminate long running workers
296 they are running. For example you might be running some long duration task in
299 informing the user of the status of running downloads.
|
| H A D | eventloops.rst | 14 stop running is *on the next iteration*, possibly later. This means that events
|
| H A D | basics.rst | 16 The event-loop usually keeps running *forever*. In pseudocode:
102 reclaim memory. Production grade projects, especially long running systems
|
| H A D | utilities.rst | 81 creation so that if it is the only watcher running then ``uv_run`` will still
97 automatically exits, even though the garbage collector is still running.
336 library and can be loaded by running our application::
|
| H A D | processes.rst | 19 running an event loop, and each process getting assigned to a separate CPU
100 will keep running after the parent process exits. See example below.
|
| H A D | networking.rst | 128 other system DHCP clients that are running on this computer on the same port.
|
| /libuv/docs/src/ |
| H A D | signal.rst | 24 resized. When a libuv app is running under a console emulator, or when a
25 32-bit libuv app is running on 64-bit system, SIGWINCH will be emulated. In
|
| H A D | stream.rst | 87 Pointer to the stream where this connection request is running.
91 Pointer to the stream where this shutdown request is running.
95 Pointer to the stream where this write request is running.
134 `server` and `client` must be handles running on the same loop.
|
| H A D | threading.rst | 124 Gets the CPU number on which the calling thread is running.
|
| H A D | process.rst | 66 * group leader, and will effectively enable the child to keep running after
|
| H A D | handle.rst | 93 Pointer to the :c:type:`uv_loop_t` the handle is running on. Readonly.
|
| /libuv/ |
| H A D | README.md | 264 When running the test from within the test driver process
268 When running the test from a child of the test driver process
292 See the section on running tests.
|
| H A D | ChangeLog | 1583 * test: disallow running the test suite as root (cjihrig)
2106 * build: support running tests in out-of-tree builds (Jameson Nash)
2285 * doc: notes on running tests, benchmarks, tools (Jamie Davis)
4172 * linux: intercept syscall when running under memory sanitizer (Keno Fischer)
5681 * test: fix fs_chown when running as root (Ben Noordhuis)
|
Completed in 67 milliseconds
