mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Clouter <alex@digriz.org.uk>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: LKML <linux-kernel@vger.kernel.org>,
	cpufreq@lists.linux.org.uk, Andrew Morton <akpm@osdl.org>,
	Dave Jones <davej@redhat.com>
Subject: Re: [patch 1/1] cpufreq_conservative: invert meaning of 'ignore_nice'
Date: Fri, 30 Sep 2005 09:09:26 +0100	[thread overview]
Message-ID: <20050930080926.GA3033@inskipp.digriz.org.uk> (raw)
In-Reply-To: <200509291346.33855.blaisorblade@yahoo.it>

[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]

Blaisorblade <blaisorblade@yahoo.it> [20050929 13:46:33 +0200]:
>
> On Thursday 29 September 2005 10:44, Alexander Clouter wrote:
> 
> > 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.
> 
'ignore_nice_tasks' gets my vote..

> 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.
> 
> This is the way we avoid problems in kernel code, when changing APIs (I read 
> Linus talking about this), so I assume it's ok?
> 
Makes a lot of sense.  I'll roll out some new patches this evening and submit 
them.

Regards

Alex

> -- 
> Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
> Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
> http://www.user-mode-linux.org/~blaisorblade
> 
> 
> 	
> 
> 	
> 		
> ___________________________________ 
> Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
> http://mail.yahoo.it

-- 
 ________________________________________ 
< An idle mind is worth two in the bush. >
 ---------------------------------------- 
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2005-09-30  8:11 UTC|newest]

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

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=20050930080926.GA3033@inskipp.digriz.org.uk \
    --to=alex@digriz.org.uk \
    --cc=akpm@osdl.org \
    --cc=blaisorblade@yahoo.it \
    --cc=cpufreq@lists.linux.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

Powered by JetHome