From 47cd216a86cab89f5a81ad6caf0fffae96979b9c Mon Sep 17 00:00:00 2001 From: Giorgos Keramidas Date: Tue, 21 Dec 2004 22:20:29 +0000 Subject: [PATCH] Redo the description of kern.quantum vs kern.sched.quantum. Joel Dahl brought kern.sched.name to my attention after my previous commit. Suggest using kern.sched.name instead of "guesswork" for 5.3-RELEASE and later versions, leaving the kern.quantum guessing in there for a while more (while we support 4.X). --- en_US.ISO8859-1/books/faq/book.sgml | 27 +++++++++++++++++---------- 1 file changed, 17 insertions(+), 10 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index 6a5f2029a7..8fbe748a53 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -5376,19 +5376,26 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr - Check if you have a sysctl for the round-robin - scheduling quantum. - This is called kern.quantum in pre-5.X - versions of &os; and kern.sched.quantum - in &os; 5.X or later. - When the sysctl exists, you will see something like this: - &prompt.user; sysctl kern.sched.quantum + If you are running &os; version 5.2.1 or earlier, check for + the existence of the kern.quantum sysctl. + If you have it, you should see something like this: + + &prompt.user; sysctl kern.quantum kern.sched.quantum: 99960 - When it does not exist, &man.sysctl.8; prints a different - message: + + If the kern.quantum sysctl exists, you are + using the 4BSD scheduler. If not, you will get an error printed + by &man.sysctl.8; (which you can safely ignore): + &prompt.user; sysctl kern.sched.quantum sysctl: unknown oid 'kern.sched.quantum' - + + In &os; version 5.3-RELEASE and later, the name of the + scheduler currently being used is directly available as the value + of the kern.sched.name sysctl: + + &prompt.user; sysctl kern.sched.name +kern.sched.name: 4BSD