From: "Matias Bjørling" <m@bjorling.me>
To: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, axboe@fb.com
Cc: keith.busch@intel.com, "Matias Bjørling" <m@bjorling.me>
Subject: [GIT PULL 0/7] LightNVM pull request for 4.9
Date: Fri, 16 Sep 2016 14:25:02 +0200 [thread overview]
Message-ID: <1474028709-30260-1-git-send-email-m@bjorling.me> (raw)
Hi Jens,
A couple of patches for 4.9. We are preparing the pblk target for
upstream, but it will have to wait for at least a cycle before it is
ready.
Geert and Arnd sent two fixes. One check for DMA and another for missing
a device_add check.
Simon added sysfs support to LightNVM. It allows the user to inspect the
geometry of a device through sysfs. As NVMe device driver integrates
with blk-mq, it also exposes the blk-mq sysfs structure.
I added a couple of plumbing patches to enable sysfs. It mainly
refactors nvme and null_blk to take control over nvm_dev and replaces
the gendisk parameter in blk_mq_(un)register_disk() with device and the
associated request queue.
Please pick up.
The patches are available here:
https://github.com/OpenChannelSSD/linux.git for-jens
Thank you,
Matias
Arnd Bergmann (1):
lightnvm: propagate device_add() error code
Geert Uytterhoeven (1):
lightnvm: NVM should depend on HAS_DMA
Matias Bjørling (4):
nvme: refactor namespaces to support non-gendisk devices
null_blk: refactor to support non-gendisk devices
blk-mq: register device instead of disk
lightnvm: control life of nvm_dev in driver
Simon A. F. Lund (1):
lightnvm: expose device geometry through sysfs
block/blk-mq-sysfs.c | 17 ++--
block/blk-sysfs.c | 4 +-
drivers/block/null_blk.c | 128 +++++++++++++++++-----------
drivers/lightnvm/Kconfig | 2 +-
drivers/lightnvm/Makefile | 2 +-
drivers/lightnvm/core.c | 55 +++++-------
drivers/lightnvm/lightnvm.h | 35 ++++++++
drivers/lightnvm/sysfs.c | 198 +++++++++++++++++++++++++++++++++++++++++++
drivers/md/dm-rq.c | 2 +-
drivers/nvme/host/core.c | 149 +++++++++++++++++++-------------
drivers/nvme/host/lightnvm.c | 33 ++++++--
drivers/nvme/host/nvme.h | 26 ++++--
include/linux/blk-mq.h | 4 +-
include/linux/lightnvm.h | 18 ++--
14 files changed, 498 insertions(+), 175 deletions(-)
create mode 100644 drivers/lightnvm/lightnvm.h
create mode 100644 drivers/lightnvm/sysfs.c
--
2.1.4
next reply other threads:[~2016-09-16 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 12:25 Matias Bjørling [this message]
2016-09-16 12:25 ` [PATCH 1/7] lightnvm: NVM should depend on HAS_DMA Matias Bjørling
2016-09-16 12:25 ` [PATCH 2/7] nvme: refactor namespaces to support non-gendisk devices Matias Bjørling
2016-09-16 12:25 ` [PATCH 3/7] null_blk: refactor " Matias Bjørling
2016-09-16 12:25 ` [PATCH 4/7] blk-mq: register device instead of disk Matias Bjørling
2016-09-16 12:25 ` [PATCH 5/7] lightnvm: control life of nvm_dev in driver Matias Bjørling
2016-09-16 12:25 ` [PATCH 6/7] lightnvm: expose device geometry through sysfs Matias Bjørling
2016-09-16 12:25 ` [PATCH 7/7] lightnvm: propagate device_add() error code Matias Bjørling
2016-09-21 14:14 ` [GIT PULL 0/7] LightNVM pull request for 4.9 Jens Axboe
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=1474028709-30260-1-git-send-email-m@bjorling.me \
--to=m@bjorling.me \
--cc=axboe@fb.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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).