diff options
author | Rickard Green <[email protected]> | 2016-06-17 11:53:29 +0200 |
---|---|---|
committer | Rickard Green <[email protected]> | 2016-06-17 11:53:29 +0200 |
commit | c9ad0c9fed1d33891f5fa8a4c4511de48417ec10 (patch) | |
tree | 791c4c7437ed9323cc3d950933f0ee91ec574699 /erts/doc/src/erl.xml | |
parent | 615b79a01706033e1ef0d78f020ebbb47fc80b86 (diff) | |
download | otp-c9ad0c9fed1d33891f5fa8a4c4511de48417ec10.tar.gz otp-c9ad0c9fed1d33891f5fa8a4c4511de48417ec10.tar.bz2 otp-c9ad0c9fed1d33891f5fa8a4c4511de48417ec10.zip |
Minor reorganization of dirty NIF documentation
Diffstat (limited to 'erts/doc/src/erl.xml')
-rw-r--r-- | erts/doc/src/erl.xml | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/erts/doc/src/erl.xml b/erts/doc/src/erl.xml index 436c2c57e1..37387f2c59 100644 --- a/erts/doc/src/erl.xml +++ b/erts/doc/src/erl.xml @@ -963,9 +963,7 @@ The amount of dirty IO schedulers is not limited by the amount of normal schedulers <seealso marker="#+SDcpu">like the amount of dirty CPU schedulers</seealso>. This since only I/O bound work is - expected to execute on dirty I/O schedulers. I/O bound jobs are - expected to either block waiting for I/O, and/or spend a limited - amount of time moving data. However, if the user should schedule CPU + expected to execute on dirty I/O schedulers. If the user should schedule CPU bound jobs on dirty I/O schedulers, these jobs might starve ordinary jobs executing on ordinary schedulers. </p> |