From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 0/7] Fixes and improvements
Date: Fri, 24 Jan 2014 16:50:47 -0700 [thread overview]
Message-ID: <1390607454-23273-1-git-send-email-keith.busch@intel.com> (raw)
Starts off the same as this one:
http://merlin.infradead.org/pipermail/linux-nvme/2014-January/000624.html
... then I kept adding more stuff and revived the percpu optimization
and hot cpu stuff and think it's in good shape.
If you want to test hot cpu, this linux-nvme tree is broken due to bad
timing on the merge from upstream during 3.13rc and merged in a scheduler
bug, so will need merge upstream or at the very least cherry-pick these:
2cce5600486 sched: Avoid NULL dereference on sd_busy
a53cb752016 sched: Assign correct scheduling domain to 'sd_llc'
Keith Busch (7):
NVMe: Namespace use after free on surprise removal
NVMe: RCU access to nvme_queue
NVMe: Initialization clean-up
NVMe: Clean-up character device bring-up
NVMe: Per-cpu IO queues
NVMe: CPU hot plug notification
NVMe: Share interrupt vectors among IO queues
drivers/block/nvme-core.c | 377 +++++++++++++++++++++++++++++++++------------
include/linux/nvme.h | 11 +-
2 files changed, 289 insertions(+), 99 deletions(-)
--
1.7.10.4
next reply other threads:[~2014-01-24 23:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 23:50 Keith Busch [this message]
2014-01-24 23:50 ` [PATCH 1/7] NVMe: Namespace use after free on surprise removal Keith Busch
2014-01-24 23:50 ` [PATCH 2/7] NVMe: RCU access to nvme_queue Keith Busch
2014-01-24 23:50 ` [PATCH 3/7] NVMe: Initialization clean-up Keith Busch
2014-01-24 23:50 ` [PATCH 4/7] NVMe: Clean-up character device bring-up Keith Busch
2014-01-24 23:50 ` [PATCH 5/7] NVMe: Per-cpu IO queues Keith Busch
2014-01-31 17:47 ` Matthew Wilcox
2014-01-24 23:50 ` [PATCH 6/7] NVMe: CPU hot plug notification Keith Busch
2014-01-24 23:50 ` [PATCH 7/7] NVMe: Share interrupt vectors among IO queues 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=1390607454-23273-1-git-send-email-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 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).