From: Arjan van de Ven <arjan@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org, a.p.zijlstra@chello.nl,
ego@in.ibm.com, tglx@linutronix.de, andi@firstfloor.org,
venkatesh.pallipadi@intel.com, vatsa@linux.vnet.ibm.com,
arun@linux.vnet.ibm.com,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [RFC PATCH 0/4] timers: framework for migration between CPU
Date: Fri, 20 Feb 2009 11:57:45 -0800 [thread overview]
Message-ID: <20090220115745.43d202d6@infradead.org> (raw)
In-Reply-To: <20090220160737.GC11294@elte.hu>
On Fri, 20 Feb 2009 17:07:37 +0100
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com> wrote:
>
> > > I'd also suggest to not do that rather ugly
> > > enable_timer_migration per-cpu variable, but simply reuse
> > > the existing nohz.load_balancer as a target CPU.
> >
> > This is a good idea to automatically bias the timers. But
> > this nohz.load_balancer is a very fast moving target and we
> > will need some heuristics to estimate overall system idleness
> > before moving the timers.
> >
> > I would agree that the power saving load balancer has a good
> > view of the system and can potentially guide the timer biasing
> > framework.
>
> Yeah, it's a fast moving target, but it already concentrates
> the load somewhat.
>
I wonder if the real answer for this isn't to have timers be considered
schedulable-entities and have the regular scheduler decide where they
actually run.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-02-20 19:57 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 12:55 [RFC PATCH 0/4] timers: framework for migration between CPU Arun R Bharadwaj
2009-02-20 12:57 ` [RFC PATCH 1/4] timers: framework to identify pinned timers Arun R Bharadwaj
2009-02-20 12:57 ` Arun R Bharadwaj
2009-02-20 12:58 ` [RFC PATCH 2/4] timers: sysfs hook to enable timer migration Arun R Bharadwaj
2009-02-20 12:58 ` Arun R Bharadwaj
2009-02-20 13:00 ` [RFC PATCH 3/4] timers: identifying the existing pinned hrtimers Arun R Bharadwaj
2009-02-20 13:00 ` Arun R Bharadwaj
2009-02-20 13:01 ` [RFC PATCH 4/4] timers: logic to enable timer migration Arun R Bharadwaj
2009-02-20 13:01 ` Arun R Bharadwaj
2009-02-20 13:21 ` [RFC PATCH 0/4] timers: framework for migration between CPU Ingo Molnar
2009-02-20 13:21 ` Ingo Molnar
2009-02-20 14:14 ` Vaidyanathan Srinivasan
2009-02-20 14:14 ` Vaidyanathan Srinivasan
2009-02-20 16:07 ` Ingo Molnar
2009-02-20 16:07 ` Ingo Molnar
2009-02-20 19:57 ` Arjan van de Ven [this message]
2009-02-20 21:53 ` Ingo Molnar
2009-02-23 7:55 ` Balbir Singh
2009-02-23 9:11 ` Ingo Molnar
2009-02-23 9:11 ` Ingo Molnar
2009-02-23 9:48 ` Balbir Singh
2009-02-23 10:22 ` Ingo Molnar
2009-02-23 10:22 ` Ingo Molnar
2009-02-23 11:24 ` Balbir Singh
2009-02-23 11:24 ` Balbir Singh
2009-02-23 10:38 ` Vaidyanathan Srinivasan
2009-02-23 10:38 ` Vaidyanathan Srinivasan
2009-02-23 11:07 ` Ingo Molnar
2009-02-23 11:25 ` Balbir Singh
2009-02-23 11:25 ` Balbir Singh
2009-02-26 8:58 ` Dipankar Sarma
2009-02-26 8:58 ` Dipankar Sarma
2009-02-26 15:45 ` Ingo Molnar
2009-02-26 16:02 ` Peter Zijlstra
2009-02-26 16:12 ` Ingo Molnar
2009-02-26 16:12 ` Ingo Molnar
2009-02-26 16:02 ` Peter Zijlstra
2009-02-26 15:45 ` Ingo Molnar
2009-02-23 11:07 ` Ingo Molnar
2009-02-23 9:48 ` Balbir Singh
2009-02-23 7:55 ` Balbir Singh
2009-02-20 21:53 ` Ingo Molnar
2009-02-20 19:57 ` Arjan van de Ven
2009-02-23 7:59 ` Arun R Bharadwaj
2009-02-23 7:59 ` Arun R Bharadwaj
-- strict thread matches above, loose matches on Subject: below --
2009-02-20 12:55 Arun R Bharadwaj
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=20090220115745.43d202d6@infradead.org \
--to=arjan@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=arun@linux.vnet.ibm.com \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--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 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.