From: David Miller <davem@davemloft.net>
To: kevdig@hypersurf.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] genirq: Set initial default irq affinity to just CPU0
Date: Sat, 25 Oct 2008 21:05:13 -0700 (PDT) [thread overview]
Message-ID: <20081025.210513.80339263.davem@davemloft.net> (raw)
In-Reply-To: <4903A37A.50607@hypersurf.com>
From: Kevin Diggs <kevdig@hypersurf.com>
Date: Sat, 25 Oct 2008 15:53:46 -0700
> What does this all mean to my GigE (dual 1.1 GHz 7455s)? Is this
> thing supposed to be able to spread irq between its cpus?
Networking interrupts should lock onto a single CPU, unconditionally.
That's the optimal way to handle networking interrupts, especially
with multiqueue chips.
This is what the userland IRQ balance daemon does.
next prev parent reply other threads:[~2008-10-26 4:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 15:57 [PATCH] genirq: Set initial default irq affinity to just CPU0 Kumar Gala
2008-10-24 15:57 ` Kumar Gala
2008-10-24 23:18 ` David Miller
2008-10-24 23:18 ` David Miller
2008-10-25 21:33 ` Benjamin Herrenschmidt
2008-10-25 21:33 ` Benjamin Herrenschmidt
2008-10-25 22:53 ` Kevin Diggs
2008-10-26 4:05 ` David Miller [this message]
2008-10-27 17:36 ` Chris Friesen
2008-10-27 18:28 ` David Miller
2008-10-27 19:10 ` Chris Friesen
2008-10-27 19:25 ` David Miller
2008-10-28 3:46 ` Chris Friesen
2008-10-27 19:43 ` Kumar Gala
2008-10-27 19:49 ` David Miller
2008-10-27 20:46 ` Kumar Gala
2008-10-26 6:48 ` Benjamin Herrenschmidt
2008-10-26 7:16 ` David Miller
2008-10-26 8:29 ` Benjamin Herrenschmidt
2008-10-27 2:30 ` Kevin Diggs
2008-10-27 2:49 ` Benjamin Herrenschmidt
2008-10-26 4:04 ` David Miller
2008-10-26 4:04 ` David Miller
2008-10-26 6:33 ` Benjamin Herrenschmidt
2008-10-26 6:33 ` Benjamin Herrenschmidt
2008-10-27 13:43 ` Kumar Gala
2008-10-27 13:43 ` Kumar Gala
2008-10-27 20:27 ` Benjamin Herrenschmidt
2008-10-27 20:27 ` Benjamin Herrenschmidt
2008-10-27 20:45 ` Kumar Gala
2008-10-27 20:45 ` Kumar Gala
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=20081025.210513.80339263.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kevdig@hypersurf.com \
--cc=linuxppc-dev@ozlabs.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 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.