From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dipankar Sarma <dipankar@in.ibm.com>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org, 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: Thu, 26 Feb 2009 17:02:49 +0100 [thread overview]
Message-ID: <1235664169.4948.319.camel@laptop> (raw)
In-Reply-To: <20090226154526.GD352@elte.hu>
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,..
next prev parent reply other threads:[~2009-02-26 16:03 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 14:14 ` Vaidyanathan Srinivasan
2009-02-20 14:14 ` Vaidyanathan Srinivasan
2009-02-20 16:07 ` Ingo Molnar
2009-02-20 19:57 ` Arjan van de Ven
2009-02-20 19:57 ` Arjan van de Ven
2009-02-20 21:53 ` Ingo Molnar
2009-02-20 21:53 ` Ingo Molnar
2009-02-23 7:55 ` Balbir Singh
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 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: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 15:45 ` Ingo Molnar
2009-02-26 16:02 ` Peter Zijlstra [this message]
2009-02-26 16:12 ` Ingo Molnar
2009-02-26 16:12 ` Ingo Molnar
2009-02-26 16:02 ` Peter Zijlstra
2009-02-20 16:07 ` Ingo Molnar
2009-02-23 7:59 ` Arun R Bharadwaj
2009-02-23 7:59 ` Arun R Bharadwaj
2009-02-20 13:21 ` Ingo Molnar
-- 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=1235664169.4948.319.camel@laptop \
--to=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=dipankar@in.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.