From: Bjorn Helgaas <helgaas@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-pci@vger.kernel.org, agordeev@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: resend: pci: automatic interrupt affinity for MSI/MSI-X capable devices V2
Date: Thu, 21 Jul 2016 16:02:23 -0500 [thread overview]
Message-ID: <20160721210223.GA11888@localhost> (raw)
In-Reply-To: <1469111423-16222-1-git-send-email-hch@lst.de>
Hi Christoph,
This thread looks like it might be a typo. It doesn't use any of the
new PCI MSI stuff. Looks like the cover letter from the PCI MSI
patches, but the actual patches are from a different series?
On Thu, Jul 21, 2016 at 04:30:20PM +0200, Christoph Hellwig wrote:
> This series adds a new set of functions that transparently use the right
> type of interrupt (MSI-X, MSI, legacy interrupt line) for a PCI device,
> and if multiple vectors are supported automatically spreads the irq
> routing to different CPUs. This will allow the block layer (and hopefully
> other consumers in the future) to use this information for mapping
> queues to fit the interrupt affinity.
>
> For the last patche to work you need to merge the irq/for-block branch of
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
>
> first.
>
> There also is a git tree available at:
>
> git://git.infradead.org/users/hch/block.git pci-irq-spreading
>
> Gitweb:
>
> http://git.infradead.org/users/hch/block.git/shortlog/refs/heads/pci-irq-spreading
>
> Since the previous post of V2 I've only added the Reviewed-by: tags from
> Alexander.
>
> Changes since V1
> - change return values for the minmum vector check
> - improve the documentation
>
> Changes since automatic interrupt affinity for MSI/MSI-X capable devices V3:
> - add PCI_IRQ_NOLEGACY flag
> - various error code fixes
> - reuse the pci_enable_msi(x)_range code instead of duplicating it
> - don't allocate msix_entry structures for the MSI-X case
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-07-21 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 14:30 resend: pci: automatic interrupt affinity for MSI/MSI-X capable devices V2 Christoph Hellwig
2016-07-21 14:30 ` [PATCH 1/3] blk-mq: don't redistribute hardware queues on a CPU hotplug event Christoph Hellwig
2016-07-21 14:30 ` [PATCH 2/3] blk-mq: only allocate a single mq_map per tag_set Christoph Hellwig
2016-07-21 14:30 ` [PATCH 3/3] blk-mq: allow the driver to pass in an affinity mask Christoph Hellwig
2016-07-21 21:02 ` Bjorn Helgaas [this message]
2016-07-21 21:08 ` resend: pci: automatic interrupt affinity for MSI/MSI-X capable devices V2 Christoph Hellwig
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=20160721210223.GA11888@localhost \
--to=helgaas@kernel.org \
--cc=agordeev@redhat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 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).