From: Andi Kleen <andi@firstfloor.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Brice Goglin <Brice.Goglin@inria.fr>,
LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [RFC] export irq_set/get_affinity() for multiqueue network drivers
Date: Fri, 29 Aug 2008 18:48:12 +0200 [thread overview]
Message-ID: <8763pjpy2b.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080829055023.07966b4a@infradead.org> (Arjan van de Ven's message of "Fri, 29 Aug 2008 05:50:23 -0700")
Arjan van de Ven <arjan@infradead.org> writes:
> On Thu, 28 Aug 2008 22:21:53 +0200
> Brice Goglin <Brice.Goglin@inria.fr> wrote:
>
>> Hello,
>>
>> Is there any way to setup IRQ masks from within a driver? myri10ge
>> currently relies on an external script (writing in
>> /proc/irq/*/smp_affinity) to bind each queue/MSI-X to a different
>> processor. By default, Linux will either:
>> * round-robin the interrupts (killing the benefit of DCA for instance)
>> * put all IRQs on the same CPU (killing much of th
>
> * do the right thing with the userspace irq balancer
It probably also needs to be hooked up the sched_mc_power_savings
When the switch is on the interrupts shouldn't be spread out over
that many sockets.
Does it need callbacks to change the interrupts when that variable
changes?
Also I suspect handling SMT explicitely is a good idea. e.g. I would
always set the affinity to all thread siblings in a core, not
just a single one, because context switch is very cheap between them.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-08-29 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 20:21 [RFC] export irq_set/get_affinity() for multiqueue network drivers Brice Goglin
2008-08-28 20:56 ` David Miller
2008-08-29 7:08 ` Brice Goglin
2008-08-29 12:50 ` Arjan van de Ven
2008-08-29 16:48 ` Andi Kleen [this message]
2008-08-29 16:52 ` Arjan van de Ven
2008-08-29 17:14 ` Rick Jones
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=8763pjpy2b.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=Brice.Goglin@inria.fr \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).