Don't suggest a silly method of detecting the scheduler when the correct
way is shown immediately above. Approved by: bcr (mentor)
This commit is contained in:
parent
6109cf2fb4
commit
b4d94bbbf4
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=40092
1 changed files with 2 additions and 4 deletions
|
|
@ -4437,10 +4437,8 @@ kern.sched.name: ULE</screen>
|
|||
|
||||
<answer>
|
||||
<para><varname>kern.sched.quantum</varname> is the maximum
|
||||
number of ticks a process can run without being preempted. It
|
||||
is specific to the 4BSD scheduler, so you can use its
|
||||
presence or absence to determine which scheduler is in
|
||||
use.</para>
|
||||
number of ticks a process can run without being preempted
|
||||
in the 4BSD scheduler.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue