From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-pci@vger.kernel.org
Cc: Matthew Wilcox <matthew@wil.cx>, Bjorn Helgaas <bhelgaas@google.com>
Subject: Improvements to MSI-X API
Date: Tue, 11 Sep 2012 13:47:18 +1000 [thread overview]
Message-ID: <1347335238.2603.12.camel@pasglop> (raw)
Hi folks !
A while back, Matthew was mentioning (iirc) some work on improving the
MSI-X APIs to be a bit less inflexible, for example by allowing setting
up individual MSI-X interrupts independently at runtime.
Is that still something being worked on ?
Another thing I've got poked about by some folks working on a new
adapter is that they would like the ability to control aliasing if we
cannot provide all the MSI-X. IE. IF the adapter has 16 sources but we
can only provide 10, they want the driver to be able to enable all 16,
but configure some of them to shoot the same message to the same
address.
This is useful in the case where the sources aren't really separate
queues but totally different type of messages, to be able to do some
fine grained control of what goes where, as the HW doesn't do that sort
of aliasing itself.
Cheers,
Ben.
next reply other threads:[~2012-09-11 3:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 3:47 Benjamin Herrenschmidt [this message]
2012-09-11 3:48 ` Improvements to MSI-X API Benjamin Herrenschmidt
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=1347335238.2603.12.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
/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).