From: Pavel Machek <pavel@suse.cz>
To: Con Kolivas <kernel@kolivas.org>
Cc: Alexander Clouter <alex-kernel@digriz.org.uk>,
akpm@osdl.org, linux-kernel@vger.kernel.org, davej@redhat.com,
davej@codemonkey.org.uk, blaisorblade@yahoo.it
Subject: Re: [patch 1/1] cpufreq_conservative/ondemand: invert meaning of 'ignore nice'
Date: Sun, 13 Nov 2005 19:59:44 +0000 [thread overview]
Message-ID: <20051113195943.GD2193@spitz.ucw.cz> (raw)
In-Reply-To: <200511110248.58751.kernel@kolivas.org>
Hi!
> > 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.
Me. I have graphics appp here (almara), that does user interaction in
separate thread from real workers. Yet you want real workers to run...
And consider notebook on ac power, using ondemand for acoustic management.
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2005-11-16 18:39 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 [this message]
2005-11-18 12:07 ` Stefan Seyfried
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=20051113195943.GD2193@spitz.ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@osdl.org \
--cc=alex-kernel@digriz.org.uk \
--cc=blaisorblade@yahoo.it \
--cc=davej@codemonkey.org.uk \
--cc=davej@redhat.com \
--cc=kernel@kolivas.org \
--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