From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Miller <davem@davemloft.net>
Cc: ossthema@de.ibm.com, shemminger@linux-foundation.org,
netdev@vger.kernel.org, themann@de.ibm.com, raisch@de.ibm.com
Subject: Re: new NAPI interface broken
Date: Tue, 16 Oct 2007 18:28:56 +1000 [thread overview]
Message-ID: <1192523336.7205.13.camel@pasglop> (raw)
In-Reply-To: <20071016.004410.85411180.davem@davemloft.net>
On Tue, 2007-10-16 at 00:44 -0700, David Miller wrote:
> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Date: Tue, 16 Oct 2007 17:29:47 +1000
>
> > Do you have any pointer to how that is done on x86 or sparc64 ?
>
> Sparc64 does it statically in the kernel.
>
> For x86, see http://irqbalance.org/
Allright, so that's an out of tree userland thingy... (which may well
work on ppc too I suppose). Definitely not installed by default by my
distro so IRQs from the network cards on all x86's using ubuntu gutsy at
least are spread to all CPUs :-)
There's also a balance kernel thread in x86 with has a notion of irq
that isn't moveable but that flag isn't set by any driver.
Cheers,
Ben.
next prev parent reply other threads:[~2007-10-16 8:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 9:37 new NAPI interface broken Jan-Bernd Themann
2007-09-12 12:50 ` David Miller
2007-09-12 13:10 ` new NAPI interface broken for POWER architecture? Christoph Raisch
2007-09-12 13:27 ` David Miller
2007-09-12 15:18 ` Arnd Bergmann
2007-10-16 7:29 ` new NAPI interface broken Benjamin Herrenschmidt
2007-10-16 7:42 ` Benjamin Herrenschmidt
2007-10-16 7:44 ` David Miller
2007-10-16 8:28 ` Benjamin Herrenschmidt [this message]
2007-10-16 8:31 ` David Miller
2007-10-16 9:01 ` Benjamin Herrenschmidt
2007-10-16 21:01 ` Anton Blanchard
2007-10-17 15:26 ` Christoph Raisch
2007-10-16 15:56 ` Arjan van de Ven
2007-09-14 22:12 ` David Miller
2007-09-18 16:15 ` Jan-Bernd Themann
2007-09-18 19:08 ` David Miller
2007-09-19 15:33 ` Roland Dreier
2007-09-19 15:43 ` Jan-Bernd Themann
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=1192523336.7205.13.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ossthema@de.ibm.com \
--cc=raisch@de.ibm.com \
--cc=shemminger@linux-foundation.org \
--cc=themann@de.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;
as well as URLs for NNTP newsgroup(s).