From: Stefan Seyfried <seife@suse.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch 1/1] cpufreq_conservative/ondemand: invert meaning of 'ignore nice'
Date: Fri, 18 Nov 2005 13:07:01 +0100 [thread overview]
Message-ID: <dlkg55$9tn$1@sea.gmane.org> (raw)
In-Reply-To: <200511110248.58751.kernel@kolivas.org>
Con Kolivas wrote:
> On Fri, 11 Nov 2005 02:11, Alexander Clouter wrote:
>> The use of the 'ignore_nice' sysfs file is confusing to anyone using it.
>> This removes the sysfs file 'ignore_nice' and in its place creates a
>> 'ignore_nice_load' entry which defaults to '1'; meaning nice'd processes
>> are not counted towards the 'business' caclulation.
>
> And just for the last time I'll argue that the default should be 0. I have yet
> to discuss this with any laptop user who thinks that 1 is the correct default
> for ondemand.
i think that 1 is the correct default for ondemand.
And i know that discussion is fruitless - everybody has its own
preference, i prefer battery runtime before almost everything else :-)
--
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, Nürnberg \ -- Leonard Cohen
next prev parent reply other threads:[~2005-11-18 12:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 15:11 [patch 1/1] cpufreq_conservative/ondemand: invert meaning of 'ignore nice' Alexander Clouter
2005-11-10 15:48 ` Con Kolivas
2005-11-10 15:54 ` Alexander Clouter
2005-11-13 19:59 ` Pavel Machek
2005-11-18 12:07 ` Stefan Seyfried [this message]
2005-11-21 15:29 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2005-11-10 17:00 Alexander Clouter
2005-11-10 23:12 ` Con Kolivas
2005-11-11 9:09 ` Alexander Clouter
2005-11-12 3:30 Pallipadi, Venkatesh
2005-11-21 18:17 Alexander Clouter
2005-11-22 1:21 ` Ken Moffat
2005-11-22 2:22 ` Dave Jones
2005-11-22 2:31 ` Con Kolivas
2005-11-22 11:43 ` Ken Moffat
2005-11-22 8:52 ` Alexander Clouter
2005-11-22 11:38 ` Ken Moffat
2005-11-23 9:46 ` Andrew Morton
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='dlkg55$9tn$1@sea.gmane.org' \
--to=seife@suse.de \
--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.