From: Matthew Wilcox <willy@linux.intel.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: "Moore, Eric" <Eric.Moore@lsi.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: MSIX and multiple reply queues
Date: Tue, 22 Jun 2010 09:59:31 -0700 [thread overview]
Message-ID: <20100622165931.GB30696@linux.intel.com> (raw)
In-Reply-To: <1277163505.10998.143.camel@mulgrave.site>
On Mon, Jun 21, 2010 at 06:38:25PM -0500, James Bottomley wrote:
> So I think what you're saying is that you plan to have one MSI-X vector
> per CPU (which is possbile)? If so, you just bind the vector affinity
> of the interrupt to the CPU you want. If it's something more complex
> than this, I'd suggest asking the PCI list ... I cc'd them in case they
> have any insight.
This is something I've been discussing with the Intel 10Gbit NIC people.
They want the same thing you do -- spread the interrupts out across the
different CPUs. I think we need an API to have the PCI subsystem set up
as many MSI-X interrupts as possible (limited by # supported by device
and # of CPUs), and spread them out across the CPUs as widely as possible
(per logical CPU if we have enough, per core, per socket, even per node).
Then we need an API to go from CPU number to MSI-X vector number.
Something else I've been musing is the idea of marking these interrupts
as per-cpu (since, well, they are). That gives an optmised interrupt
handler path in __do_IRQ. It's going to make the ->set_affinity handler
significantly different, but it seems worth doing.
No idea when I'll have time to do this ...
prev parent reply other threads:[~2010-06-22 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4565AEA676113A449269C2F3A549520F3FF6C887@cosmail03.lsi.com>
2010-06-21 23:38 ` MSIX and multiple reply queues James Bottomley
2010-06-22 6:08 ` Grant Grundler
2010-06-22 16:59 ` Matthew Wilcox [this message]
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=20100622165931.GB30696@linux.intel.com \
--to=willy@linux.intel.com \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@suse.de \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@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 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.