From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Alexander Clouter <alex@digriz.org.uk>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org,
blaisorblade@yahoo.it, davej@codemonkey.org.uk, davej@redhat.com
Subject: Re: [patch 1/1] cpufreq_conservative/ondemand: invert meaning of 'ignore nice'
Date: Tue, 22 Nov 2005 01:21:18 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.63.0511220102330.18504@deepthought.mydomain> (raw)
In-Reply-To: <20051121181722.GA2599@inskipp.digriz.org.uk>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed, Size: 1247 bytes --]
On Mon, 21 Nov 2005, 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' calculation.
>
> WARNING: this obvious breaks any userland tools that expected ignore_nice' to
> exist, to draw attention to this fact it was concluded on the mailing list
> that the entry should be removed altogether so the userland app breaks and so
> the author can build simple to detect workaround. Having said that it seems
> currently very few tools even make use of this functionality; all I could
> find was a Gentoo Wiki entry.
>
> Signed-off-by: Alexander Clouter <alex-kernel@digriz.org.uk>
>
Great. I get to rewrite my initscript for the ondemand governor to
test for yet another kernel version, and write a 0 to yet another sysfs
file, just so that any compile I start in an xterm on my desktop box can
make the processor work for its living.
Just what have you cpufreq guys got against nice'd processes ? It's
enough to drive a man to powernowd ;)
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
next prev parent reply other threads:[~2005-11-22 1:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 18:17 Alexander Clouter
2005-11-22 1:21 ` Ken Moffat [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-11-12 3:30 Pallipadi, Venkatesh
2005-11-10 17:00 Alexander Clouter
2005-11-10 23:12 ` Con Kolivas
2005-11-11 9:09 ` Alexander Clouter
2005-11-10 15:11 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
2005-11-21 15:29 ` Dave Jones
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=Pine.LNX.4.63.0511220102330.18504@deepthought.mydomain \
--to=zarniwhoop@ntlworld.com \
--cc=akpm@osdl.org \
--cc=alex@digriz.org.uk \
--cc=blaisorblade@yahoo.it \
--cc=davej@codemonkey.org.uk \
--cc=davej@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®