From: Frank Rowand <frank.rowand@am.sony.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Arjan van de Ven <arjan@infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Prevent users from disabling tickless
Date: Wed, 22 Dec 2010 13:00:37 -0800 [thread overview]
Message-ID: <4D1266F5.8040702@am.sony.com> (raw)
In-Reply-To: <20101221233942.GL1263@parisc-linux.org>
On 12/21/10 15:39, Matthew Wilcox wrote:
>
> Disabling NO_HZ has a serious negative effect on performance -- an extra
> 70us per I/O. Prevent users from deselecting it.
>
> Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
>
> diff --git a/kernel/time/Kconfig b/kernel/time/Kconfig
> index f06a8a3..55b9a04 100644
> --- a/kernel/time/Kconfig
> +++ b/kernel/time/Kconfig
> @@ -5,13 +5,9 @@ config TICK_ONESHOT
> bool
>
> config NO_HZ
> - bool "Tickless System (Dynamic Ticks)"
> + def_bool y
> depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
> select TICK_ONESHOT
> - help
> - This option enables a tickless system: timer interrupts will
> - only trigger on an as-needed basis both when the system is
> - busy and when the system is idle.
>
> config HIGH_RES_TIMERS
> bool "High Resolution Timer Support"
Why remove the ability to make the configuration choice? Why not
just add the info about performance impact to the help text and
let me shoot myself in the foot (that is the unix way (tm)) if
I desire to?
(Yes I say your later reply about the kernel command line method
of shooting myself in the foot.)
-Frank
next prev parent reply other threads:[~2010-12-22 21:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 23:39 [PATCH] Prevent users from disabling tickless Matthew Wilcox
2010-12-21 23:46 ` Rafael J. Wysocki
2010-12-22 0:24 ` Matthew Wilcox
2010-12-22 0:38 ` Rafael J. Wysocki
2010-12-22 21:00 ` Frank Rowand [this message]
2010-12-22 21:34 ` Matthew Wilcox
2010-12-22 22:32 ` Frank Rowand
2010-12-26 22:22 ` Len Brown
2010-12-26 23:20 ` Grant Coady
2010-12-26 23:23 ` Regarding kernel work queue issues Raj Kumar
2010-12-25 15:42 ` [PATCH] Prevent users from disabling tickless Stefan Richter
2011-01-02 8:57 ` Pavel Machek
2011-01-02 9:15 ` Eric Dumazet
2011-01-02 10:59 ` Serge Belyshev
2011-01-02 11:06 ` Remy Bohmer
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=4D1266F5.8040702@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox