|
Lines 5355-5360
Link Here
|
| 5355 |
</itemizedlist> |
5355 |
</itemizedlist> |
| 5356 |
</answer> |
5356 |
</answer> |
| 5357 |
</qandaentry> |
5357 |
</qandaentry> |
|
|
5358 |
|
| 5359 |
<qandaentry> |
| 5360 |
<question id="scheduler-in-use"> |
| 5361 |
<para>How can I verify which scheduler is in use on a running system?</para> |
| 5362 |
</question> |
| 5363 |
|
| 5364 |
<answer> |
| 5365 |
<para>Just type: |
| 5366 |
<screen>&prompt.root; <userinput>sysctl kern.quantum</userinput></screen> |
| 5367 |
If you see |
| 5368 |
<screen>unknown oid 'kern.quantum'</screen> |
| 5369 |
it means that you use new <quote>SCHED_ULE</quote> scheduler, but |
| 5370 |
if you see |
| 5371 |
<screen>kern.quantum: 100000</screen> |
| 5372 |
that means your system runs under old <quote>SCHED_4BSD</quote> scheduler. |
| 5373 |
</para> |
| 5374 |
</answer> |
| 5375 |
</qandaentry> |
| 5376 |
|
| 5377 |
<qandaentry> |
| 5378 |
<question id="scheduler-kern-quantum"> |
| 5379 |
<para>What does it mean 'kern.quantum'?</para> |
| 5380 |
</question> |
| 5381 |
|
| 5382 |
<answer> |
| 5383 |
<para>It is the maximum number of ticks a process can run without being |
| 5384 |
preempted. It is specific to the 4BSD scheduler, so you can use it |
| 5385 |
presence or absence to determine which scheduler is in use. |
| 5386 |
</para> |
| 5387 |
</answer> |
| 5388 |
</qandaentry> |
| 5358 |
</qandaset> |
5389 |
</qandaset> |
| 5359 |
</chapter> |
5390 |
</chapter> |