From: Christoph Hellwig <hch@lst.de>
To: tglx@linutronix.de, linux-block@vger.kernel.org,
linux-pci@vger.kernel.org
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: RFC: automatic interrupt affinity for MSI/MSI-X capable devices
Date: Fri, 15 Apr 2016 18:35:44 -0700 [thread overview]
Message-ID: <1460770552-31260-1-git-send-email-hch@lst.de> (raw)
This series enhances the irq and PCI code to allow spreading around MSI and
MSI-X vectors so that they have per-cpu affinity if possible, or at least
per-node. For that it takes the algorithm from blk-mq, moves it to
a common place, and makes it available through a vastly simplified PCI
interrupt allocation API. It then switches blk-mq to be able to pick up
the queue mapping from the device if available, and demostrates all this
using the NVMe driver.
There is still some work todo, mostly related to handling PCI hotplug,
more details are in the individual patches.
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: RFC: automatic interrupt affinity for MSI/MSI-X capable devices
Date: Fri, 15 Apr 2016 18:35:44 -0700 [thread overview]
Message-ID: <1460770552-31260-1-git-send-email-hch@lst.de> (raw)
This series enhances the irq and PCI code to allow spreading around MSI and
MSI-X vectors so that they have per-cpu affinity if possible, or at least
per-node. For that it takes the algorithm from blk-mq, moves it to
a common place, and makes it available through a vastly simplified PCI
interrupt allocation API. It then switches blk-mq to be able to pick up
the queue mapping from the device if available, and demostrates all this
using the NVMe driver.
There is still some work todo, mostly related to handling PCI hotplug,
more details are in the individual patches.
next reply other threads:[~2016-04-16 1:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-16 1:35 Christoph Hellwig [this message]
2016-04-16 1:35 ` RFC: automatic interrupt affinity for MSI/MSI-X capable devices Christoph Hellwig
2016-04-16 1:35 ` [PATCH 1/8] device: Add irq affinity hint cpumask pointer Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-16 1:35 ` [PATCH 2/8] genirq: Make use of dev->irq_affinity Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-16 1:35 ` [PATCH 3/8] genirq: add a helper spread an affinity mask for MSI/MSI-X vectors Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-16 1:35 ` [PATCH 4/8] genirq: add a helper to program the pre-set affinity mask into the controller Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-16 1:35 ` [PATCH 5/8] blk-mq: allow the driver to pass in an affinity mask Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-16 1:35 ` [PATCH 6/8] pci: provide sensible irq vector alloc/free routines Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-29 21:16 ` Bjorn Helgaas
2016-04-29 21:16 ` Bjorn Helgaas
2016-05-01 18:01 ` Christoph Hellwig
2016-05-01 18:01 ` Christoph Hellwig
2016-05-02 13:11 ` Bjorn Helgaas
2016-05-02 13:11 ` Bjorn Helgaas
2016-05-02 14:42 ` Christoph Hellwig
2016-05-02 14:42 ` Christoph Hellwig
2016-05-02 15:29 ` Bjorn Helgaas
2016-05-02 15:29 ` Bjorn Helgaas
2016-05-03 21:19 ` Christoph Hellwig
2016-05-03 21:19 ` Christoph Hellwig
2016-05-03 21:37 ` Bjorn Helgaas
2016-05-03 21:37 ` Bjorn Helgaas
2016-04-16 1:35 ` [PATCH 7/8] pci: spread interrupt vectors in pci_alloc_irq_vectors Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-18 8:30 ` Thomas Gleixner
2016-04-18 8:30 ` Thomas Gleixner
2016-04-16 1:35 ` [PATCH 8/8] nvme: switch to use pci_alloc_irq_vectors Christoph Hellwig
2016-04-16 1:35 ` 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=1460770552-31260-1-git-send-email-hch@lst.de \
--to=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.