From: keith.busch@intel.com (Keith Busch)
Subject: [PATCHv2 0/4] NVMe IRQ sets fixups
Date: Thu, 3 Jan 2019 15:50:29 -0700 [thread overview]
Message-ID: <20190103225033.11249-1-keith.busch@intel.com> (raw)
Changes from v1:
Added documentation to Documentation/PCI/MSI-HOWTO.txt
Grammar, spelling, and format fixes to commit logs and code comments.
Keith Busch (4):
nvme-pci: Set tagset nr_maps just once
nvme-pci: Distribute io queue types after creation
PCI/MSI: Handle vector reduce and retry
nvme-pci: Use PCI to handle IRQ reduce and retry
Documentation/PCI/MSI-HOWTO.txt | 36 +++++++++++-
drivers/nvme/host/pci.c | 126 +++++++++++++++++++---------------------
drivers/pci/msi.c | 20 ++-----
include/linux/interrupt.h | 5 ++
4 files changed, 107 insertions(+), 80 deletions(-)
--
2.14.4
WARNING: multiple messages have this Message-ID (diff)
From: Keith Busch <keith.busch@intel.com>
To: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>, Ming Lei <ming.lei@redhat.com>,
linux-nvme@lists.infradead.org,
Bjorn Helgaas <helgaas@kernel.org>,
linux-pci@vger.kernel.org
Cc: Keith Busch <keith.busch@intel.com>
Subject: [PATCHv2 0/4] NVMe IRQ sets fixups
Date: Thu, 3 Jan 2019 15:50:29 -0700 [thread overview]
Message-ID: <20190103225033.11249-1-keith.busch@intel.com> (raw)
Changes from v1:
Added documentation to Documentation/PCI/MSI-HOWTO.txt
Grammar, spelling, and format fixes to commit logs and code comments.
Keith Busch (4):
nvme-pci: Set tagset nr_maps just once
nvme-pci: Distribute io queue types after creation
PCI/MSI: Handle vector reduce and retry
nvme-pci: Use PCI to handle IRQ reduce and retry
Documentation/PCI/MSI-HOWTO.txt | 36 +++++++++++-
drivers/nvme/host/pci.c | 126 +++++++++++++++++++---------------------
drivers/pci/msi.c | 20 ++-----
include/linux/interrupt.h | 5 ++
4 files changed, 107 insertions(+), 80 deletions(-)
--
2.14.4
next reply other threads:[~2019-01-03 22:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 22:50 Keith Busch [this message]
2019-01-03 22:50 ` [PATCHv2 0/4] NVMe IRQ sets fixups Keith Busch
2019-01-03 22:50 ` [PATCHv2 1/4] nvme-pci: Set tagset nr_maps just once Keith Busch
2019-01-03 22:50 ` Keith Busch
2019-01-04 1:46 ` Ming Lei
2019-01-04 1:46 ` Ming Lei
2019-01-03 22:50 ` [PATCHv2 2/4] nvme-pci: Distribute io queue types after creation Keith Busch
2019-01-03 22:50 ` Keith Busch
2019-01-04 2:31 ` Ming Lei
2019-01-04 2:31 ` Ming Lei
2019-01-04 7:21 ` Ming Lei
2019-01-04 7:21 ` Ming Lei
2019-01-04 15:53 ` Keith Busch
2019-01-04 15:53 ` Keith Busch
2019-01-04 18:17 ` Christoph Hellwig
2019-01-04 18:17 ` Christoph Hellwig
2019-01-04 18:35 ` Keith Busch
2019-01-04 18:35 ` Keith Busch
2019-01-06 2:56 ` Ming Lei
2019-01-06 2:56 ` Ming Lei
2019-01-03 22:50 ` [PATCHv2 3/4] PCI/MSI: Handle vector reduce and retry Keith Busch
2019-01-03 22:50 ` Keith Busch
2019-01-04 2:45 ` Ming Lei
2019-01-04 2:45 ` Ming Lei
2019-01-04 22:35 ` Bjorn Helgaas
2019-01-04 22:35 ` Bjorn Helgaas
2019-01-04 22:56 ` Keith Busch
2019-01-04 22:56 ` Keith Busch
2019-01-03 22:50 ` [PATCHv2 4/4] nvme-pci: Use PCI to handle IRQ " Keith Busch
2019-01-03 22:50 ` Keith Busch
2019-01-04 2:41 ` Ming Lei
2019-01-04 2:41 ` Ming Lei
2019-01-04 18:19 ` Christoph Hellwig
2019-01-04 18:19 ` Christoph Hellwig
2019-01-04 18:33 ` Keith Busch
2019-01-04 18:33 ` Keith Busch
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=20190103225033.11249-1-keith.busch@intel.com \
--to=keith.busch@intel.com \
/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.