From: Con Kolivas <kernel@kolivas.org>
To: linux list <linux-kernel@vger.kernel.org>
Cc: ck list <ck@vds.kolivas.org>
Subject: [ckpatch][15/29] hz-no_default_250.patch
Date: Sun, 18 Jun 2006 17:32:48 +1000 [thread overview]
Message-ID: <200606181732.48952.kernel@kolivas.org> (raw)
Make 250 HZ a value that is not selected by default and give some better
recommendations in help.
Signed-off-by: Con Kolivas <kernel@kolivas.org>
kernel/Kconfig.hz | 15 +++++++++------
1 files changed, 9 insertions(+), 6 deletions(-)
Index: linux-ck-dev/kernel/Kconfig.hz
===================================================================
--- linux-ck-dev.orig/kernel/Kconfig.hz 2006-06-18 15:23:58.000000000 +1000
+++ linux-ck-dev/kernel/Kconfig.hz 2006-06-18 15:24:28.000000000 +1000
@@ -21,14 +21,17 @@ choice
help
100 HZ is a typical choice for servers, SMP and NUMA systems
with lots of processors that may show reduced performance if
- too many timer interrupts are occurring.
+ too many timer interrupts are occurring. Laptops may also show
+ improved battery life.
- config HZ_250
+ config HZ_250_NODEFAULT
bool "250 HZ"
help
- 250 HZ is a good compromise choice allowing server performance
- while also showing good interactive responsiveness even
- on SMP and NUMA systems.
+ 250 HZ is a lousy compromise choice allowing server interactivity
+ while also showing desktop throughput and no extra power saving on
+ laptops. Good for when you can't make up your mind.
+
+ Recommend 100 or 1000 instead.
config HZ_1000
bool "1000 HZ"
@@ -41,6 +44,6 @@ endchoice
config HZ
int
default 100 if HZ_100
- default 250 if HZ_250
+ default 250 if HZ_250_NODEFAULT
default 1000 if HZ_1000
--
-ck
next reply other threads:[~2006-06-18 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 7:32 Con Kolivas [this message]
2006-06-18 7:42 ` [ckpatch][15/29] hz-no_default_250.patch Willy Tarreau
2006-06-18 10:08 ` Con Kolivas
2006-06-18 15:03 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2006-06-19 0:52 Albert Cahalan
2006-06-19 1:25 ` Con Kolivas
2006-06-19 11:52 ` Jan Engelhardt
2006-06-21 4:53 ` Con Kolivas
2006-06-19 1:30 ` Lee Revell
2006-06-19 1:52 ` Con Kolivas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200606181732.48952.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.