From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
linux-kernel@vger.kernel.org, vatsa@linux.vnet.ibm.com,
andi@firstfloor.org, arun@linux.vnet.ibm.com,
linux-pm@lists.linux-foundation.org, tglx@linutronix.de,
Arjan van de Ven <arjan@infradead.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [RFC PATCH 0/4] timers: framework for migration between CPU
Date: Thu, 26 Feb 2009 17:12:55 +0100 [thread overview]
Message-ID: <20090226161255.GA15390@elte.hu> (raw)
In-Reply-To: <1235664169.4948.319.camel@laptop>
* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Thu, 2009-02-26 at 16:45 +0100, Ingo Molnar wrote:
>
> > Yes - but that kind of policy should be coupled and expressed
> > via cpusets. /proc based irq_affinity is just a limited,
> > inflexible hack. All things IRQ partitioning should be handled
> > via cpusets - perhaps via the 'system sets' idea from Peter?
>
> all we got out of that idea was the default_smp_affinity thing
> in /proc/irq and a head-ache trying to work out silly details.
>
> Maybe we ought to try again,..
Your system sets patch was actually very sane, it just fell
victim to a merge window i think. Mind re-sending it?
Ingo
next prev parent reply other threads:[~2009-02-26 16:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090220125516.GB10232@linux.vnet.ibm.com>
2009-02-20 12:57 ` [RFC PATCH 1/4] timers: framework to identify pinned timers 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 13:00 ` [RFC PATCH 3/4] timers: identifying the existing pinned hrtimers 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:21 ` [RFC PATCH 0/4] timers: framework for migration between CPU Ingo Molnar
[not found] ` <20090220132145.GF26418@elte.hu>
2009-02-20 14:14 ` Vaidyanathan Srinivasan
[not found] ` <20090220141415.GA27381@dirshya.in.ibm.com>
2009-02-20 16:07 ` Ingo Molnar
[not found] ` <20090220160737.GC11294@elte.hu>
2009-02-20 19:57 ` Arjan van de Ven
[not found] ` <20090220115745.43d202d6@infradead.org>
2009-02-20 21:53 ` Ingo Molnar
[not found] ` <20090220215318.GA30665@elte.hu>
2009-02-23 7:55 ` Balbir Singh
[not found] ` <20090223075521.GA3725@balbir.in.ibm.com>
2009-02-23 9:11 ` Ingo Molnar
[not found] ` <20090223091158.GJ9582@elte.hu>
2009-02-23 9:48 ` Balbir Singh
[not found] ` <20090223094850.GA10226@balbir.in.ibm.com>
2009-02-23 10:22 ` Ingo Molnar
2009-02-23 10:38 ` Vaidyanathan Srinivasan
[not found] ` <20090223103814.GB8817@dirshya.in.ibm.com>
2009-02-23 11:07 ` Ingo Molnar
[not found] ` <20090223110725.GB17312@elte.hu>
2009-02-23 11:25 ` Balbir Singh
2009-02-26 8:58 ` Dipankar Sarma
[not found] ` <20090226085831.GA28397@in.ibm.com>
2009-02-26 15:45 ` Ingo Molnar
[not found] ` <20090226154526.GD352@elte.hu>
2009-02-26 16:02 ` Peter Zijlstra
[not found] ` <1235664169.4948.319.camel@laptop>
2009-02-26 16:12 ` Ingo Molnar [this message]
[not found] ` <20090223102234.GQ9582@elte.hu>
2009-02-23 11:24 ` Balbir Singh
2009-02-23 7:59 ` Arun R Bharadwaj
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=20090226161255.GA15390@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=arun@linux.vnet.ibm.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.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