From: "Matias Bjørling" <m@bjorling.me> To: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, axboe@fb.com, keith.busch@intel.com, linux-nvme@lists.infradead.org Cc: "Matias Bjørling" <m@bjorling.me> Subject: [PATCH 0/6] sysfs support for LightNVM Date: Fri, 10 Jun 2016 14:20:56 +0200 [thread overview] Message-ID: <1465561262-13789-1-git-send-email-m@bjorling.me> (raw) Hi Jens and Keith, If the patches look good to you, would you pick them up through your tree? The common way to expose a storage device is to export it through the gendisk structure, which takes care of handling the visibility lifetime of the device to user-space and carries device driver and block layer specific sysfs entries. For LightNVM, no gendisk is exposed, which hides these entries. This patchset enables LightNVM to expose a subset of the gendisk entries by implementing a new non-gendisk device that only exposes the sysfs entries that are relevant to the device driver and LightNVM. For example /mq and the NVMe sysfs entries. The new non-gendisk exposes itself in place of the original gendisk. Thus, a gendisk device exposed through /sys/class/nvme/nvme0n1, will still be exposed through the same directory, although only with the /mq, lightnvm, and nvme specific entries. The LightNVM storage device can be found through sysfs by searching for devices that has the "lightnvm" dev type. v2: - Updated "expose gennvm target type" to expose its own kobject, which pblk and others can hook into. - Fixed missing disk_name in null_blk patch on lightnvm device Thanks, Matias 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: let drivers control the lifetime of nvm_dev Simon A. F. Lund (2): lightnvm: expose device geometry through sysfs lightnvm: expose gennvm target type through sysfs block/blk-mq-sysfs.c | 13 ++- block/blk-sysfs.c | 4 +- drivers/block/null_blk.c | 128 +++++++++++++++++----------- drivers/lightnvm/Makefile | 2 +- drivers/lightnvm/core.c | 52 +++++------- drivers/lightnvm/gennvm.c | 112 +++++++++++++++++++++---- drivers/lightnvm/lightnvm.h | 35 ++++++++ drivers/lightnvm/sysfs.c | 195 +++++++++++++++++++++++++++++++++++++++++++ drivers/md/dm.c | 2 +- drivers/nvme/host/core.c | 165 ++++++++++++++++++++---------------- drivers/nvme/host/lightnvm.c | 29 ++++++- drivers/nvme/host/nvme.h | 26 ++++-- include/linux/blk-mq.h | 4 +- include/linux/lightnvm.h | 28 +++++-- 14 files changed, 597 insertions(+), 198 deletions(-) create mode 100644 drivers/lightnvm/lightnvm.h create mode 100644 drivers/lightnvm/sysfs.c -- 2.1.4
WARNING: multiple messages have this Message-ID (diff)
From: m@bjorling.me (Matias Bjørling) Subject: [PATCH 0/6] sysfs support for LightNVM Date: Fri, 10 Jun 2016 14:20:56 +0200 [thread overview] Message-ID: <1465561262-13789-1-git-send-email-m@bjorling.me> (raw) Hi Jens and Keith, If the patches look good to you, would you pick them up through your tree? The common way to expose a storage device is to export it through the gendisk structure, which takes care of handling the visibility lifetime of the device to user-space and carries device driver and block layer specific sysfs entries. For LightNVM, no gendisk is exposed, which hides these entries. This patchset enables LightNVM to expose a subset of the gendisk entries by implementing a new non-gendisk device that only exposes the sysfs entries that are relevant to the device driver and LightNVM. For example /mq and the NVMe sysfs entries. The new non-gendisk exposes itself in place of the original gendisk. Thus, a gendisk device exposed through /sys/class/nvme/nvme0n1, will still be exposed through the same directory, although only with the /mq, lightnvm, and nvme specific entries. The LightNVM storage device can be found through sysfs by searching for devices that has the "lightnvm" dev type. v2: - Updated "expose gennvm target type" to expose its own kobject, which pblk and others can hook into. - Fixed missing disk_name in null_blk patch on lightnvm device Thanks, Matias 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: let drivers control the lifetime of nvm_dev Simon A. F. Lund (2): lightnvm: expose device geometry through sysfs lightnvm: expose gennvm target type through sysfs block/blk-mq-sysfs.c | 13 ++- block/blk-sysfs.c | 4 +- drivers/block/null_blk.c | 128 +++++++++++++++++----------- drivers/lightnvm/Makefile | 2 +- drivers/lightnvm/core.c | 52 +++++------- drivers/lightnvm/gennvm.c | 112 +++++++++++++++++++++---- drivers/lightnvm/lightnvm.h | 35 ++++++++ drivers/lightnvm/sysfs.c | 195 +++++++++++++++++++++++++++++++++++++++++++ drivers/md/dm.c | 2 +- drivers/nvme/host/core.c | 165 ++++++++++++++++++++---------------- drivers/nvme/host/lightnvm.c | 29 ++++++- drivers/nvme/host/nvme.h | 26 ++++-- include/linux/blk-mq.h | 4 +- include/linux/lightnvm.h | 28 +++++-- 14 files changed, 597 insertions(+), 198 deletions(-) create mode 100644 drivers/lightnvm/lightnvm.h create mode 100644 drivers/lightnvm/sysfs.c -- 2.1.4
next reply other threads:[~2016-06-10 12:21 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-06-10 12:20 Matias Bjørling [this message] 2016-06-10 12:20 ` [PATCH 0/6] sysfs support for LightNVM Matias Bjørling 2016-06-10 12:20 ` [PATCH 1/6] nvme: refactor namespaces to support non-gendisk devices Matias Bjørling 2016-06-10 12:20 ` Matias Bjørling 2016-06-10 12:20 ` Matias Bjørling 2016-06-10 12:20 ` [PATCH 2/6] null_blk: refactor " Matias Bjørling 2016-06-10 12:20 ` Matias Bjørling 2016-06-10 12:20 ` Matias Bjørling 2016-06-10 12:20 ` [PATCH 3/6] blk-mq: register device instead of disk Matias Bjørling 2016-06-10 12:20 ` Matias Bjørling 2016-06-10 12:21 ` [PATCH 4/6] lightnvm: let drivers control the lifetime of nvm_dev Matias Bjørling 2016-06-10 12:21 ` Matias Bjørling 2016-06-10 12:21 ` Matias Bjørling
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=1465561262-13789-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 \ --cc=linux-nvme@lists.infradead.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: linkBe 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.