public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: vatsa@linux.vnet.ibm.com, Tomasz Chmielewski <mangoo@wpkg.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	a.p.zijlstra@chello.nl, dhaval@linux.vnet.ibm.com
Subject: Re: (ondemand) CPU governor  regression between 2.6.23 and 2.6.24
Date: Mon, 28 Jan 2008 09:38:27 +0100	[thread overview]
Message-ID: <479D9483.9090907@aitel.hist.no> (raw)
In-Reply-To: <200801271757.07743.toralf.foerster@gmx.de>

Toralf Förster wrote:
> At Sunday 27 January 2008 Srivatsa Vaddagiri wrote :
>   
>> You can set that to 0 to ask ondemand gov to include nice load into
>> account while calculating cpu freq changes:
>>
>> # echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load
>>
>> This should restore the behavior of ondemand governor as seen in 2.6.23
>> in your case (even with CONFIG_FAIR_GROUP_SCHED enabled). Can you pls confirm 
>> if that happens?
>>     
>
> Yes, of course, unfortunately this speeds up the CPU up to max power consumption
> which isn't wanted at least at a notebook b/c temperature and fan speed are at
> maximum in that case :-(
>
> It would be nice to run a grid application at lowest priority without impact to
> power / fan / temperature but OTOH have full performance for desktop
> applications, isn't it ?
>   
In theory, the fix is simple:
If _non-niced_ tasks use more than 80% of the cputime _made available to 
them_,
then  increase the processor speed.

The cputime allocated to niced tasks (that may be cpu intensive but 
shouldn't
cause max speed on their own) won't matter then.

Helge Hafting

  parent reply	other threads:[~2008-01-28  8:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-26 17:11 (ondemand) CPU governor regression between 2.6.23 and 2.6.24 Tomasz Chmielewski
2008-01-26 18:46 ` Toralf Förster
2008-01-27 14:46   ` Srivatsa Vaddagiri
2008-01-27 15:06     ` Toralf Förster
2008-01-27 16:54       ` Srivatsa Vaddagiri
2008-01-27 16:57         ` Toralf Förster
2008-01-27 21:27           ` Peter Zijlstra
2008-01-27 22:32             ` Ingo Molnar
2008-01-28  8:38           ` Helge Hafting [this message]
2008-01-26 21:38 ` Toralf Förster
2008-01-26 21:45   ` Sam Ravnborg
     [not found] ` <200801271200.04971.toralf.foerster@gmx.de>
     [not found]   ` <1201433167.22060.10.camel@homer.simson.net>
2008-01-27 12:39     ` Toralf Förster
2008-01-27 18:58       ` Mike Galbraith
2008-01-27 21:14         ` Toralf Förster
2008-01-27 21:25           ` Peter Zijlstra
2008-01-28 13:18           ` Ingo Molnar
2008-01-28 15:16             ` Toralf Förster
  -- strict thread matches above, loose matches on Subject: below --
2008-01-26 14:06 Toralf Förster
2008-02-04  0:32 ` Andrew Morton
2008-02-04  0:36   ` Andrew Morton
2008-02-04 17:44   ` Pallipadi, Venkatesh
2008-02-04 19:18     ` Toralf Förster

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=479D9483.9090907@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mangoo@wpkg.org \
    --cc=mingo@elte.hu \
    --cc=toralf.foerster@gmx.de \
    --cc=vatsa@linux.vnet.ibm.com \
    /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