os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Clean up some confusing text and clarify that sched_pin/unpin only operate

Browse source 
on curthread on the current CPU.  Reference sched_bind/unbind for those
looking for something more general.
This commit is contained in:
John Baldwin 2005-05-12 21:24:42 +00:00
parent 5c855039bf
commit cd44ed208a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=24566
1 changed files with 6 additions and 5 deletions

11
en_US.ISO8859-1/books/arch-handbook/smp/chapter.sgml
View file

@ -456,11 +456,12 @@
<varname>td_pinned</varname> does not need any locking. The
<function>sched_pin</function> function increments the nesting
count and <function>sched_unpin</function> decrements the
nesting count. Due to the locking requirements specified
above, they will only operate on the current thread and thus
would not need to handle the case of making a thread
migrateable that currently resides on a per-CPU run
queue.</para>
nesting count. Note that these functions only operate on the
current thread and bind the current thread to the CPU it is
executing on at the time. To bind an arbitrary thread to a
specific CPU, the <function>sched_bind</function> and
<function>sched_unbind</function> functions should be used
instead.</para>
</sect2>
<sect2>