Attachment 30006 Details for Bug 50720 – file.diff

[patch] file.diff

file.diff (text/plain), 1.61 KB, created by osa on 2003-04-08 13:30:08 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: osa

Created: 2003-04-08 13:30:08 UTC

Size: 1.61 KB

patch

obsolete

>Index: doc/en_US.ISO8859-1/books/faq/book.sgml
>===================================================================
>RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/faq/book.sgml,v
>retrieving revision 1.526
>diff -u -r1.526 book.sgml
>--- doc/en_US.ISO8859-1/books/faq/book.sgml	7 Apr 2003 18:37:59 -0000	1.526
>+++ doc/en_US.ISO8859-1/books/faq/book.sgml	8 Apr 2003 11:58:22 -0000
>@@ -5355,6 +5355,37 @@
>           </itemizedlist>
>         </answer>
>       </qandaentry>
>+
>+      <qandaentry>
>+        <question id="scheduler-in-use">
>+          <para>How can I verify which scheduler is in use on a running system?</para>
>+        </question>
>+
>+        <answer>
>+          <para>Just type:
>+            <screen>&prompt.root; <userinput>sysctl kern.quantum</userinput></screen>
>+            If you see
>+            <screen>unknown oid 'kern.quantum'</screen>
>+            it means that you use new <quote>SCHED_ULE</quote> scheduler, but
>+            if you see
>+            <screen>kern.quantum: 100000</screen>
>+	     that means your system runs under old <quote>SCHED_4BSD</quote> scheduler.
>+          </para>
>+        </answer>
>+      </qandaentry>
>+
>+      <qandaentry>
>+        <question id="scheduler-kern-quantum">
>+          <para>What does it mean 'kern.quantum'?</para>
>+        </question>
>+
>+        <answer>
>+          <para>It is the maximum number of ticks a process can run without being
>+            preempted.  It is specific to the 4BSD scheduler, so you can use it
>+            presence or absence to determine which scheduler is in use.
>+          </para>
>+        </answer>
>+      </qandaentry>
>     </qandaset>
>   </chapter>

Actions: View | Diff

Attachments on bug 50720: 30006