From: ebiederm@xmission.com (Eric W. Biederman)
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-pci@vger.kernel.org, jbarnes@virtuousgeek.org,
linux-kernel@vger.kernel.org
Subject: Re: Support for multiple MSI
Date: Wed, 04 Mar 2009 06:52:39 -0800 [thread overview]
Message-ID: <m17i35z6fc.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <1235410082-5016-1-git-send-email-matthew@wil.cx> (Matthew Wilcox's message of "Mon\, 23 Feb 2009 12\:27\:56 -0500")
Matthew Wilcox <matthew@wil.cx> writes:
> Currently, Linux supports multiple MSI-X interrupts per device, but only
> a single MSI interrupt. This patch series adds support to the generic
> PCI code for supporting multiple MSI interrupts. Architectures will
> need to add support for multiple MSIs, and I have a patch to do that for
> x86 (which needs some more work). Getting this patch series in first
> is important so we can start supporting this interface in drivers and
> architectures independently.
Do we have any benchmarks anywhere that show that multiple msi support
gains us something?
The requirement to allocate a contiguous block of vector numbers worries
me for the x86 implementation. I don't like the idea of having to deal
with allocations that can fail because of fragmentation.
The fact that we also can not honor the irq affinity properly for multiple
msi also disturbs me.
At a quick skim your patchset is only the generic code without a single
architecture specific implementation so it appears you have not done the
hard work on figuring out how to deal with multiple msi in the real
world.
Given that msi-x does not have any of these issues without data to say
that there is a true gain in supporting multi-msi I don't see the point
of supporting it.
Eric
next prev parent reply other threads:[~2009-03-04 14:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 17:27 Support for multiple MSI Matthew Wilcox
2009-02-23 17:27 ` [PATCH 1/6] Rewrite MSI-HOWTO Matthew Wilcox
2009-02-24 20:00 ` Randy Dunlap
2009-02-24 20:28 ` Matthew Wilcox
2009-02-24 20:55 ` Randy Dunlap
2009-02-25 7:34 ` Sitsofe Wheeler
2009-02-27 6:15 ` Grant Grundler
2009-02-27 12:14 ` Matthew Wilcox
2009-03-01 23:46 ` Michael Ellerman
2009-03-02 20:33 ` Grant Grundler
2009-03-02 21:01 ` Matthew Wilcox
2009-02-23 17:27 ` [PATCH 2/6] PCI MSI: Replace 'type' with 'is_msix' Matthew Wilcox
2009-03-03 0:16 ` Michael Ellerman
2009-02-23 17:27 ` [PATCH 3/6] PCI MSI: msi_desc->dev is always initialised Matthew Wilcox
2009-02-23 17:28 ` [PATCH 4/6] PCI MSI: Use mask_pos instead of mask_base when appropriate Matthew Wilcox
2009-02-23 17:28 ` [PATCH 5/6] PCI MSI: Refactor interrupt masking code Matthew Wilcox
2009-03-03 0:16 ` Michael Ellerman
2009-03-16 21:01 ` Matthew Wilcox
2009-02-23 17:28 ` [PATCH 6/6] PCI MSI: Add support for multiple MSI Matthew Wilcox
2009-03-03 0:16 ` Michael Ellerman
2009-03-16 21:07 ` Matthew Wilcox
2009-03-04 14:52 ` Eric W. Biederman [this message]
2009-03-04 22:26 ` Support " Matthew Wilcox
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=m17i35z6fc.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--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