From: Ming Lei <ming.lei@redhat.com>
To: Christoph Hellwig <hch@lst.de>,
Bjorn Helgaas <helgaas@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, Keith Busch <keith.busch@intel.com>
Subject: Re: [PATCH 0/5] genirq/affinity: introduce .setup_affinity to support allocating interrupt sets
Date: Fri, 25 Jan 2019 17:56:19 +0800 [thread overview]
Message-ID: <20190125095617.GA17754@ming.t460p> (raw)
In-Reply-To: <20190125095347.17950-1-ming.lei@redhat.com>
On Fri, Jan 25, 2019 at 05:53:42PM +0800, Ming Lei wrote:
> Hi,
>
> The current support for allocating interrupt sets requires that same 'max_vec'
> and 'min_vec' is passed to pci_alloc_irq_vectors_affinity(), then driver has to
> try to allocate again and again until it succeeds.
>
> This patch introduces .setup_affinity callback, and we can use it to
> re-caculate interrupt sets and build affinity for each set after
> irq vectors are allocated.
>
> Turns out both genirq/affinity and nvme code get simplified a lot.
>
> Please review and comment!
>
> Ming Lei (5):
> genirq/affinity: move allocation of 'node_to_cpumask' to
> irq_build_affinity_masks
> genirq/affinity: allow driver to setup managed IRQ's affinity
> genirq/affinity: introduce irq_build_affinity()
> nvme-pci: simplify nvme_setup_irqs() via .setup_affinity callback
> genirq/affinity: remove support for allocating interrupt sets
>
> drivers/nvme/host/pci.c | 97 +++++++++++++++++++++--------------------
> drivers/pci/msi.c | 14 ------
> include/linux/interrupt.h | 42 ++++++++++++------
> kernel/irq/affinity.c | 108 ++++++++++++++++++++++++----------------------
> 4 files changed, 133 insertions(+), 128 deletions(-)
oops, forget to CC Keith.
Thanks,
Ming
prev parent reply other threads:[~2019-01-25 9:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 9:53 [PATCH 0/5] genirq/affinity: introduce .setup_affinity to support allocating interrupt sets Ming Lei
2019-01-25 9:53 ` [PATCH 1/5] genirq/affinity: move allocation of 'node_to_cpumask' to irq_build_affinity_masks Ming Lei
2019-02-07 22:02 ` Bjorn Helgaas
2019-01-25 9:53 ` [PATCH 2/5] genirq/affinity: allow driver to setup managed IRQ's affinity Ming Lei
2019-02-07 22:21 ` Bjorn Helgaas
2019-02-10 9:22 ` Ming Lei
2019-02-10 16:30 ` Thomas Gleixner
2019-02-11 3:54 ` Ming Lei
2019-02-11 14:39 ` Bjorn Helgaas
2019-02-11 22:38 ` Thomas Gleixner
2019-02-12 11:17 ` Ming Lei
2019-01-25 9:53 ` [PATCH 3/5] genirq/affinity: introduce irq_build_affinity() Ming Lei
2019-01-25 9:53 ` [PATCH 4/5] nvme-pci: simplify nvme_setup_irqs() via .setup_affinity callback Ming Lei
2019-02-10 16:39 ` Thomas Gleixner
2019-02-11 3:58 ` Ming Lei
2019-02-10 18:49 ` Thomas Gleixner
2019-02-11 4:09 ` Ming Lei
2019-01-25 9:53 ` [PATCH 5/5] genirq/affinity: remove support for allocating interrupt sets Ming Lei
2019-02-07 22:22 ` Bjorn Helgaas
2019-01-25 9:56 ` Ming Lei [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=20190125095617.GA17754@ming.t460p \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=helgaas@kernel.org \
--cc=keith.busch@intel.com \
--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=sagi@grimberg.me \
--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 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).