public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Alexander Clouter <alex@digriz.org.uk>,
	LKML <linux-kernel@vger.kernel.org>,
	cpufreq@lists.linux.org.uk, Andrew Morton <akpm@osdl.org>,
	alex-kernel@digriz.org.uk
Subject: Re: [patch 1/1] cpufreq_conservative: invert meaning of 'ignore_nice'
Date: Thu, 29 Sep 2005 17:51:53 -0400	[thread overview]
Message-ID: <20050929215153.GF31516@redhat.com> (raw)
In-Reply-To: <200509291346.33855.blaisorblade@yahoo.it>

On Thu, Sep 29, 2005 at 01:46:33PM +0200, Blaisorblade wrote:
 > On Thursday 29 September 2005 10:44, Alexander Clouter wrote:
 > > The use of the 'ignore_nice' sysfs file is confusing to anyone using.  This
 > > patch makes it so when you now set it to the default value of 1, process
 > > nice time is also ignored in the cpu 'busyness' calculation.
 > 
 > > Prior to this patch to set it to '1' to make process nice time count...even
 > > confused me :)
 > 
 > > WARNING: this obvious breaks any userland tools that expect things to be
 > > the other way round.  This patch clears up the confusion but should go in
 > > ASAP as at the moment it seems very few tools even make use of this
 > > functionality; all I could find was a Gentoo Wiki entry.
 > 
 > My suggestion on this is to rename the flag too, as ignore_nice_load (or 
 > ignore_nice_tasks, choose your way). Don't forget to do it in docs too.
 > 
 > So userspace tools will error out rather than do the reverse of what they were 
 > doing, and the user will fix the thing according to the (new) docs.

Agreed. If we change this, we change it completely.
Stefan already mentioned his app will break, and we typically don't
find out about widespread breakage until after we ship a release.

		Dave


  reply	other threads:[~2005-09-29 21:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29  8:44 [patch 1/1] cpufreq_conservative: invert meaning of 'ignore_nice' Alexander Clouter
2005-09-29 11:46 ` Blaisorblade
2005-09-29 21:51   ` Dave Jones [this message]
2005-09-30 13:56     ` Stefan Seyfried
2005-09-30  8:09   ` Alexander Clouter

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=20050929215153.GF31516@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@osdl.org \
    --cc=alex-kernel@digriz.org.uk \
    --cc=alex@digriz.org.uk \
    --cc=blaisorblade@yahoo.it \
    --cc=cpufreq@lists.linux.org.uk \
    --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