archive mirror
 help / color / mirror / Atom feed
From: Minwoo Im <>
Cc: "Keith Busch" <>, "Jens Axboe" <>,
	"Christoph Hellwig" <>,
	"Sagi Grimberg" <>,
	"Javier González" <>,
	"Minwoo Im" <>
Subject: [PATCH 0/1] nvme: introduce generic per-namespace chardev
Date: Thu, 25 Mar 2021 21:30:47 +0900	[thread overview]
Message-ID: <> (raw)


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

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
        /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.


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(-)


Linux-nvme mailing list

             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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).