mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: dipankar@in.ibm.com, balbir@linux.vnet.ibm.com,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Suresh B Siddha <suresh.b.siddha@intel.com>,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	Ingo Molnar <mingo@elte.hu>, Vatsa <vatsa@linux.vnet.ibm.com>,
	Gautham R Shenoy <ego@in.ibm.com>
Subject: Re: [RFC v1] Tunable sched_mc_power_savings=n
Date: Fri, 27 Jun 2008 09:51:30 +0200	[thread overview]
Message-ID: <1214553090.2801.7.camel@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <48641A7D.6080204@firstfloor.org>

On Fri, 2008-06-27 at 00:38 +0200, Andi Kleen wrote:
> Peter Zijlstra wrote:
> 
> >> And your workload manager could just nice processes. It should probably
> >> do that anyways to tell ondemand you don't need full frequency.
> > 
> > Except that I want my nice 19 distcc processes to utilize as much cpu as
> > possible, but just not bother any other stuff I might be doing...
> 
> They already won't do that if you run ondemand and cpufreq. It won't
> crank up the frequency for niced processes.
> 
> Extending that existing policy to socket load balancing would be only
> natural.

There used to be an option for them to also up on niced load. If that
disappeared then I'd call that a huge usability regression. Basically
making ondemand useless.

/me checks,..

Yeah, on F9, my opteron runs at 1GHz when idle, but when I start distcc,
which like said runs on nice 19, the cpu speed goes up to 2.4GHz.

And it uses the ondemand govenor.


  parent reply	other threads:[~2008-06-27  7:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25 19:11 Vaidyanathan Srinivasan
2008-06-26 13:49 ` Andi Kleen
2008-06-26 15:01   ` Dipankar Sarma
2008-06-26 18:31     ` Vaidyanathan Srinivasan
2008-06-26 15:01   ` Balbir Singh
2008-06-26 18:08     ` Andi Kleen
2008-06-26 18:52       ` Vaidyanathan Srinivasan
2008-06-26 19:37         ` David Collier-Brown
2008-06-27  6:50           ` Vaidyanathan Srinivasan
2008-06-26 20:17         ` Andi Kleen
2008-06-26 21:00           ` Dipankar Sarma
2008-06-26 21:37             ` Andi Kleen
2008-06-26 21:43               ` Peter Zijlstra
2008-06-26 22:38                 ` Andi Kleen
2008-06-27  6:24                   ` Vaidyanathan Srinivasan
2008-06-27  7:51                   ` Peter Zijlstra [this message]
2008-06-27  8:06                     ` Andi Kleen
2008-06-28 11:35                       ` Tim Connors
2008-06-28 11:55                         ` Andi Kleen
2008-06-28 12:22                       ` Matthew Garrett
2008-06-28 12:36                         ` Andi Kleen
2008-06-28 12:53                           ` Matthew Garrett
2008-06-28 11:22                   ` Tim Connors
2008-06-29 18:02                     ` David Collier-Brown
2008-06-30  4:57                       ` Vaidyanathan Srinivasan
2008-06-30  5:55                         ` Tim Connors
2008-06-30 14:18                         ` David Collier-Brown
2008-06-30 14:31                           ` Andi Kleen
2008-06-27  4:54               ` Dipankar Sarma
2008-06-27  8:03                 ` Andi Kleen
2008-06-30 16:10                   ` Dipankar Sarma
2008-06-27  7:19           ` Vaidyanathan Srinivasan
2008-06-27  4:15       ` Balbir Singh
2008-06-27  8:08 ` KOSAKI Motohiro
2008-06-27  8:50   ` Vaidyanathan Srinivasan
2008-06-27 12:54   ` David Collier-Brown

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=1214553090.2801.7.camel@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=andi@firstfloor.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=dipankar@in.ibm.com \
    --cc=ego@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=vatsa@linux.vnet.ibm.com \
    --cc=venkatesh.pallipadi@intel.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

Powered by JetHome