All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
To: Mike Chan <mike@android.com>
Cc: Peter Zijlstra <peterz@infradead.org>, Salman <sqazi@google.com>,
	mingo@elte.hu, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, linux-pm@lists.linux-foundation.org,
	arjan@infradead.org, csadler@google.com, ranjitm@google.com,
	kenchen@google.com, dawnchen@google.com
Subject: Re: [PATCH 0/3] [idled]: Idle Cycle Injector for power capping
Date: Fri, 23 Apr 2010 00:32:08 +0530	[thread overview]
Message-ID: <20100422190208.GD10750@dirshya.in.ibm.com> (raw)
In-Reply-To: <v2v8bb80c381004211832o88258fdez8e640ad9a45d11c0@mail.gmail.com>

* Mike Chan <mike@android.com> [2010-04-21 18:32:22]:

> On Thu, Apr 15, 2010 at 12:51 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Tue, 2010-04-13 at 17:08 -0700, Salman wrote:
> >> As we discussed earlier this year, Google has an implementation that it
> >> would like to share.  I have finally gotten around to porting it to
> >> v2.6.33 and cleaning up the interfaces.  It is provided in the following
> >> messages for your review.  I realize that when we first discussed this
> >> idea, a lot of ideas were presented for enhancing it.  Thanks alot for
> >> your suggestions.  I haven't gotten around to implementing any of them.
> >
> > .33 is way too old to submit patches against.
> >
> > That said, I really really dislike this approach, I would much rather
> > see it tie in with power aware scheduling.
> 
> I may have missed this on lkml but are there any on-going community
> efforts to power aware scheduling?

Yes, mostly in power aware task placement and task consolidation in
large SMP systems and also some timer consolidation to improve low
power idle residency.

There are some tuning and optimizations in cpuidle governor that is
related to power management but not core scheduler.

As Peter mentioned, most of them may not apply to uni processor
systems.

--Vaidy

  parent reply	other threads:[~2010-04-22 19:02 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14  0:08 [PATCH 0/3] [idled]: Idle Cycle Injector for power capping Salman
2010-04-14  0:08 ` [PATCH 1/3] [kidled]: introduce kidled Salman
2010-04-14  9:49   ` Andi Kleen
2010-04-14  9:49   ` Andi Kleen
2010-04-14 15:41     ` Salman Qazi
2010-04-14 15:41     ` Salman Qazi
2010-04-15  7:46       ` Peter Zijlstra
2010-04-15  7:46       ` Peter Zijlstra
2010-04-14  0:08 ` Salman
2010-04-14  0:08 ` [PATCH 2/3] [kidled]: Add eager injection Salman
2010-04-14  0:08 ` Salman
2010-04-14  0:08 ` [PATCH 3/3] [kidled]: Introduce power capping priority and LB awareness Salman
2010-04-14  0:08 ` Salman
2010-04-15  7:51 ` [PATCH 0/3] [idled]: Idle Cycle Injector for power capping Peter Zijlstra
2010-04-15  7:51 ` Peter Zijlstra
2010-04-17 17:08   ` tytso
2010-04-17 17:08   ` tytso
2010-04-17 17:57     ` Arjan van de Ven
2010-04-17 17:57     ` Arjan van de Ven
2010-04-17 19:51     ` Peter Zijlstra
2010-04-17 19:51     ` Peter Zijlstra
2010-04-19 17:20   ` Salman Qazi
2010-04-19 19:01     ` Peter Zijlstra
2010-04-19 19:01     ` Peter Zijlstra
2010-04-20  1:00       ` Arjan van de Ven
2010-04-20  5:00         ` Vaidyanathan Srinivasan
2010-04-20  5:00         ` Vaidyanathan Srinivasan
2010-04-20  1:00       ` Arjan van de Ven
2010-04-20  4:50       ` Vaidyanathan Srinivasan
2010-04-20  4:50       ` Vaidyanathan Srinivasan
2010-04-20 17:52         ` Salman Qazi
2010-04-21  5:08           ` Arjan van de Ven
2010-04-21  5:08           ` Arjan van de Ven
2010-04-20 17:52         ` Salman Qazi
2010-04-19 17:20   ` Salman Qazi
2010-04-22  1:32   ` Mike Chan
2010-04-22  8:21     ` Peter Zijlstra
2010-04-22  8:21     ` Peter Zijlstra
2010-04-22 19:02     ` Vaidyanathan Srinivasan
2010-04-22 19:02     ` Vaidyanathan Srinivasan [this message]
2010-04-22  1:32   ` Mike Chan
2010-04-17 16:40 ` Arjan van de Ven
2010-04-17 16:40 ` Arjan van de Ven
  -- strict thread matches above, loose matches on Subject: below --
2010-04-14  0:08 Salman

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=20100422190208.GD10750@dirshya.in.ibm.com \
    --to=svaidy@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=csadler@google.com \
    --cc=dawnchen@google.com \
    --cc=kenchen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mike@android.com \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=ranjitm@google.com \
    --cc=sqazi@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.