From: Matthew Wilcox <matthew@wil.cx>
To: Frank Rowand <frank.rowand@am.sony.com>
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 14:34:03 -0700 [thread overview]
Message-ID: <20101222213403.GP1263@parisc-linux.org> (raw)
In-Reply-To: <4D1266F5.8040702@am.sony.com>
On Wed, Dec 22, 2010 at 01:00:37PM -0800, Frank Rowand wrote:
> 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?
$ wc -l .config
2601 .config
It's too hard to get every single config option right ... unless it's a
works / doesn't work choice, having a "make my performance suck" config
option is a bad idea. I didn't even know I had this config option
set the wrong way until I ran powertop on my desktop, implemented its
recommendations for things I'd screwed up in my .config, then reran the
tests I was doing.
Someone with a big server might not run powertop, so wouldn't be
told they'd got it run. Sure, we could write a special tool to
check peoples config options to see if they've got some common
config options set wrongly ... but I'm rather reminded of Brazil.
http://farm1.static.flickr.com/50/109556460_5362c5f2b5_o.jpg
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2010-12-22 21:34 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
2010-12-22 21:34 ` Matthew Wilcox [this message]
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=20101222213403.GP1263@parisc-linux.org \
--to=matthew@wil.cx \
--cc=arjan@infradead.org \
--cc=frank.rowand@am.sony.com \
--cc=linux-kernel@vger.kernel.org \
--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