diff options
| author | Mohamed Edrah <43171151+MSE99@users.noreply.github.com> | 2021-07-29 18:08:53 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-07-29 12:08:53 -0400 |
| commit | 84c057a357bcf5f67ba3fdfde3e8e22e1693074f (patch) | |
| tree | 871f58593a9317ceff44de9f2dd8737636f43fa4 /docs/src | |
| parent | bd7fcf1bfc411c4a57141002f97a163d6a00a925 (diff) | |
| download | libuv-84c057a357bcf5f67ba3fdfde3e8e22e1693074f.tar.gz libuv-84c057a357bcf5f67ba3fdfde3e8e22e1693074f.zip | |
docs: fix wrong information about scheduling
Fixes: https://github.com/libuv/libuv/issues/3252
PR-URL: https://github.com/libuv/libuv/pull/3253
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Jameson Nash <vtjnash@gmail.com>
Diffstat (limited to 'docs/src')
| -rw-r--r-- | docs/src/guide/basics.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/src/guide/basics.rst b/docs/src/guide/basics.rst index e55a20cf..457fb15c 100644 --- a/docs/src/guide/basics.rst +++ b/docs/src/guide/basics.rst @@ -42,7 +42,7 @@ as other activities and other I/O operations are kept waiting. One of the standard solutions is to use threads. Each blocking I/O operation is started in a separate thread (or in a thread pool). When the blocking function -gets invoked in the thread, the processor can schedule another thread to run, +gets invoked in the thread, the operating system can schedule another thread to run, which actually needs the CPU. The approach followed by libuv uses another style, which is the **asynchronous, |