From: Len Brown <lenb@kernel.org>
To: Frank Rowand <frank.rowand@am.sony.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
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: Sun, 26 Dec 2010 17:22:40 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1012261708070.2945@x980> (raw)
In-Reply-To: <4D1266F5.8040702@am.sony.com>
> 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?
One can argue that configurability is one of the greatest
strengths of Linux. OTOH, one can also argue that users
tend to get lost and hang themselves when given too
much rope; and that the burden of support and maintenance
of unnecessary config options squanders valuable resources.
Personally, I have two bugs filed against my code that
can be reproduced only in tickfull mode that almost
nobody uses. Is it a good use of my time to be
distracted by by configurations that 0.01% use,
or focus on issues seen by the other 99.99%?
I'm in favor of deleting the config option,
and the cmdline option with it, and I applaud
Matthew for proposing such.
Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-12-26 22:23 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
2010-12-22 22:32 ` Frank Rowand
2010-12-26 22:22 ` Len Brown [this message]
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=alpine.LFD.2.00.1012261708070.2945@x980 \
--to=lenb@kernel.org \
--cc=arjan@infradead.org \
--cc=frank.rowand@am.sony.com \
--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