Home
last modified time | relevance | path

Searched refs:after (Results 1 – 25 of 29) sorted by relevance

12

/libuv/test/
H A Dbenchmark-fs-stat.c65 uint64_t after; in sync_bench() local
75 after = uv_hrtime(); in sync_bench()
79 (after - before) / 1e9, in sync_bench()
80 fmt(&fmtbuf[1], (1.0 * NUM_SYNC_REQS) / ((after - before) / 1e9))); in sync_bench()
99 uint64_t after; in async_bench() local
114 after = uv_hrtime(); in async_bench()
119 (after - before) / 1e9, in async_bench()
120 fmt(&fmtbuf[1], (1.0 * NUM_ASYNC_REQS) / ((after - before) / 1e9))); in async_bench()
/libuv/docs/code/progress/
H A Dmain.c26 void after(uv_work_t *req, int status) { in after() function
44 uv_queue_work(loop, &req, fake_download, after); in main()
/libuv/docs/src/
H A Dstream.rst32 behaviour. It is safe to reuse the ``uv_write_t`` object only after the
58 Callback called after data was written on a stream. `status` will be 0 in
63 Callback called after a connection started by :c:func:`uv_connect` is done.
68 Callback called after a shutdown request has been completed. `status` will
112 after shutdown is complete.
124 connections. Call this function after receiving a :c:type:`uv_connection_cb`
246 is changed after write requests have already been submitted. Therefore it is
247 recommended to set the blocking mode immediately after opening or creating
H A Dtimer.rst42 If `repeat` is non-zero, the callback fires first after `timeout`
43 milliseconds and then repeatedly after `repeat` milliseconds.
H A Dcheck.rst8 after polling for i/o.
H A Dmisc.rst263 after all resources have been freed and thus libuv doesn't reference
289 .. warning:: Don't call libuv functions after calling
298 freeing `base` after the uv_buf_t is done. Return struct passed by value.
858 after reading from `/dev/random` once, or the `KERN_RANDOM`
861 or `/dev/urandom` after reading from `/dev/random` once.
864 if available, or `/dev/urandom` after reading from `/dev/random` once.
867 - Other UNIX: `/dev/urandom` after reading from `/dev/random` once.
870 `buf` is undefined after an error.
893 Get the length of a UTF-16 (or UCS-2) `utf16` value after converting it to
909 `wtf8_ptr` must contain an extra space for an extra NUL after the result.
[all …]
H A Dprocess.rst66 * group leader, and will effectively enable the child to keep running after
175 The PID of the spawned process. It's set after calling :c:func:`uv_spawn`.
182 Callback called after the process exits.
H A Dasync.rst61 :c:func:`uv_async_send` is called again after the callback was called, it will be called
H A Dhandle.rst144 Request handle to be closed. `close_cb` will be called asynchronously after
146 Moreover, the memory can only be released in `close_cb` or after it has
280 after calling :c:func:`uv_timer_start`.
H A Dthreadpool.rst46 thread after the work on the threadpool has been completed. If the work
H A Dfs_poll.rst22 after the handle is started, when any change happens to the monitored path.
H A Ddesign.rst72 #. Pending callbacks are called. All I/O callbacks are called right after polling for I/O, for the
97 #. Check handle callbacks are called. Check handles get their callbacks called right after the
H A Dloop.rst203 Reinitialize any kernel state necessary in the child process after
220 created in the child process after the fork should not use this
H A Dfs_event.rst42 after the handle is started.
H A Dmigration_010_100.rst8 is a migration guide for the most significant changes that happened after 0.10
H A Derrors.rst288 cannot send after transport endpoint shutdown
H A Dpoll.rst28 closed immediately after a call to :c:func:`uv_poll_stop` or :c:func:`uv_close`.
/libuv/
H A DMakefile.am219 test/test-not-writable-after-shutdown.c \
268 test/test-tcp-close-after-read-timeout.c \
272 test/test-tcp-connect-error-after-write.c \
282 test/test-tcp-shutdown-after-write.c \
286 test/test-tcp-write-after-connect.c \
H A DChangeLog66 * udp,unix: fix sendmsg use-after-free (Geddy)
395 * unix: reset signal counters after fork (SmorkalovG)
940 * process: fix hang after NOTE_EXIT (Jameson Nash)
1122 * stream: permit read after seeing EOF (Jameson Nash)
1183 * test: fix stack-use-after-scope (Zhao Zhili)
3008 * zos: reset epoll data after fork (jBarz)
3059 * test: clean up semaphore after use (jBarz)
5225 * stream: start thread after assignments (Oguz Bastemur)
5336 * stream: start thread after assignments (Oguz Bastemur)
5367 * process: close stdio after dup2'ing it (Fedor Indutny)
[all …]
H A DCMakeLists.txt592 test/test-not-writable-after-shutdown.c
640 test/test-tcp-close-after-read-timeout.c
644 test/test-tcp-connect-error-after-write.c
656 test/test-tcp-shutdown-after-write.c
661 test/test-tcp-write-after-connect.c
/libuv/docs/src/guide/
H A Dutilities.rst12 Timers invoke the callback after a certain time has elapsed since the timer was
26 will start a repeating timer, which first starts 5 seconds (the ``timeout``) after the execution
80 other watchers are done. In that case just unref the timer immediately after
96 Observe how after 9 seconds, when the fake job is done, the program
123 for a brief amount as the loop deals with the input data, after which it will
230 interval, after which we should drive libcurl forward regardless of I/O status.
H A Dthreads.rst234 ``uv_work_t`` structure and once the function returns, the *after* function
270 For tasks that do get cancelled successfully, the *after* function is called
316 may be invoked immediately after ``uv_async_send`` is called in another
317 thread, or it may be invoked after some time. libuv may also combine
320 least once* after the call to ``uv_async_send``. If you have no pending
H A Dnetworking.rst91 where ``on_connect`` will be called after the connection is established. The
207 after ``uv_getaddrinfo`` returns. The `hostname`, `servname` and `hints`
H A Dbasics.rst101 close loops since the program quits after the loop ends and the system will
195 structure that is passed to the callback after the write is done.
H A Dprocesses.rst65 It is **required** to close the process watcher after the process exits.
100 will keep running after the parent process exits. See example below.
232 that every client is sent ten ticks after which that connection is closed.

Completed in 40 milliseconds

12