From: Andi Kleen <andi@firstfloor.org>
To: Peter Zijlstra <peterz@infradead.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>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
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 00:38:53 +0200 [thread overview]
Message-ID: <48641A7D.6080204@firstfloor.org> (raw)
In-Reply-To: <1214516584.12265.10.camel@twins.programming.kicks-ass.net>
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.
-Andi
next prev parent reply other threads:[~2008-06-26 22:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 19:11 [RFC v1] Tunable sched_mc_power_savings=n 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 [this message]
2008-06-27 6:24 ` Vaidyanathan Srinivasan
2008-06-27 7:51 ` Peter Zijlstra
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=48641A7D.6080204@firstfloor.org \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--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=peterz@infradead.org \
--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