From: Minwoo Im <minwoo.im.dev@gmail.com>
To: linux-nvme@lists.infradead.org
Cc: "Keith Busch" <kbusch@kernel.org>, "Jens Axboe" <axboe@fb.com>,
"Christoph Hellwig" <hch@lst.de>,
"Sagi Grimberg" <sagi@grimberg.me>,
"Javier González" <javier.gonz@samsung.com>,
"Minwoo Im" <minwoo.im.dev@gmail.com>
Subject: [PATCH 0/1] nvme: introduce generic per-namespace chardev
Date: Thu, 25 Mar 2021 21:30:47 +0900 [thread overview]
Message-ID: <20210325123048.94784-1-minwoo.im.dev@gmail.com> (raw)
Hello,
This patch introduces per-namespace character device to I/O in case that
blkdev is not initialized properly. Userspace applications are able to
I/O to the generic namespace chardev even there's no blkdev properly
initialized.
This patch is derived from Javier's patch series [1]. Changes from the
previous version are:
- Update naming convention for the chardev exactly the same with the
blkdev:
/dev/nvme-generic-XcYnZ to /dev/nvme-generic-XnY
- Re-consider the multipath support. Rather than exposing all the
path-specific namespace path with controller(e.g., nvmeXcYnZ), only
expose head namespace instance in case of multipath. Otherwise, it
will expose all the blkdevs created.
[1] https://lore.kernel.org/linux-nvme/20210301192452.16770-1-javier.gonz@samsung.com/
Minwoo Im (1):
nvme: introduce generic per-namespace chardev
drivers/nvme/host/core.c | 170 +++++++++++++++++++++++++++++++++-
drivers/nvme/host/multipath.c | 17 ++++
drivers/nvme/host/nvme.h | 25 +++++
3 files changed, 209 insertions(+), 3 deletions(-)
--
2.27.0
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-03-25 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 12:30 Minwoo Im [this message]
2021-03-25 12:30 ` [PATCH 1/1] nvme: introduce generic per-namespace chardev Minwoo Im
2021-03-29 8:31 ` Kanchan Joshi
2021-03-29 11:56 ` Minwoo Im
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=20210325123048.94784-1-minwoo.im.dev@gmail.com \
--to=minwoo.im.dev@gmail.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=javier.gonz@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.