diff options
author | Jakub Jelinek <jakub@redhat.com> | 2008-08-29 07:42:08 +0000 |
---|---|---|
committer | Jakub Jelinek <jakub@redhat.com> | 2008-08-29 07:42:08 +0000 |
commit | 315a43aa949b25896c511fa6e2efd6be57e2e01d (patch) | |
tree | 625aa5d40df04b92dcd3bd8128d30e52a45975ac /manual/resource.texi | |
parent | 2fb513c60061821c7e5e7fb6014d2afd0308b7e9 (diff) |
Updated to fedora-glibc-20080828T1623cvs/fedora-glibc-2_8_90-12
Diffstat (limited to 'manual/resource.texi')
-rw-r--r-- | manual/resource.texi | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/manual/resource.texi b/manual/resource.texi index aabd28976a..4a814c9e4a 100644 --- a/manual/resource.texi +++ b/manual/resource.texi @@ -591,7 +591,7 @@ ready to execute instructions right now. When a process blocks to wait for something like I/O, its absolute priority is irrelevant. @cindex runnable process -@strong{Note:} The term ``runnable'' is a synonym for ``ready to run.'' +@strong{NB:} The term ``runnable'' is a synonym for ``ready to run.'' When two processes are running or ready to run and both have the same absolute priority, it's more interesting. In that case, who gets the @@ -663,7 +663,7 @@ privileged process constantly monitors the process' CPU usage and raises its absolute priority when the process isn't getting its entitled share and lowers it when the process is exceeding it. -@strong{Note:} The absolute priority is sometimes called the ``static +@strong{NB:} The absolute priority is sometimes called the ``static priority.'' We don't use that term in this manual because it misses the most important feature of the absolute priority: its absoluteness. |