From: javier@javigon.com To: linux-nvme@lists.infradead.org Cc: linux-block@vger.kernel.org, hch@lst.de, kbusch@kernel.org, sagi@grimberg.me, minwoo.im.dev@gmail.com, "Javier González" <javier.gonz@samsung.com> Subject: [PATCH V5 0/2] nvme: enable char device per namespace Date: Mon, 22 Feb 2021 20:01:05 +0100 [thread overview] Message-ID: <20210222190107.8479-1-javier.gonz@samsung.com> (raw) From: Javier González <javier.gonz@samsung.com> These two patches enable a char device per namespace, also through multipath. It is possible to test this in QEMU using Keith's and Klaus' tree in nvme-next http://git.infradead.org/qemu-nvme.git/shortlog/refs/heads/nvme-next Keith: Regarding nvme-cli support, once this is in place, we will send a patch to nvme-cli so that this device is shown in verbose mode. Do you have anu thoughts about this? Changes since V4 - Added support for multipath (from Minwoo) - Fixed typo in commit message for sysfs naming - Rebase into nvme-5.12 Changes since V3 - Use a dedicated ida for the generic handle - Do not abort namespace greation if the generic handle fails Changes since V2: - Apply a number of naming and code structure improvements (from Christoph) - Use i_cdev to pull struct nvme_ns in the ioctl path instead of populating file->private_data (from Christoph) - Change char device and sysfs entries to /dev/nvme-generic-XcYnZ to follow the hidden device naming scheme (from Christoph and Keith) Changes since V1: - Remove patches 1-3 which are already picked up by Christoph - Change the char device and sysfs entries to nvmeXnYc / c signals char device - Address Minwoo's comments on inline functions and style Javier González (1): nvme: enable char device per namespace Minwoo Im (1): nvme: allow open for nvme-generic char device drivers/nvme/host/core.c | 173 +++++++++++++++++++++++++++++++++++---- drivers/nvme/host/nvme.h | 9 ++ 2 files changed, 165 insertions(+), 17 deletions(-) -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: javier@javigon.com To: linux-nvme@lists.infradead.org Cc: sagi@grimberg.me, linux-block@vger.kernel.org, minwoo.im.dev@gmail.com, kbusch@kernel.org, "Javier González" <javier.gonz@samsung.com>, hch@lst.de Subject: [PATCH V5 0/2] nvme: enable char device per namespace Date: Mon, 22 Feb 2021 20:01:05 +0100 [thread overview] Message-ID: <20210222190107.8479-1-javier.gonz@samsung.com> (raw) From: Javier González <javier.gonz@samsung.com> These two patches enable a char device per namespace, also through multipath. It is possible to test this in QEMU using Keith's and Klaus' tree in nvme-next http://git.infradead.org/qemu-nvme.git/shortlog/refs/heads/nvme-next Keith: Regarding nvme-cli support, once this is in place, we will send a patch to nvme-cli so that this device is shown in verbose mode. Do you have anu thoughts about this? Changes since V4 - Added support for multipath (from Minwoo) - Fixed typo in commit message for sysfs naming - Rebase into nvme-5.12 Changes since V3 - Use a dedicated ida for the generic handle - Do not abort namespace greation if the generic handle fails Changes since V2: - Apply a number of naming and code structure improvements (from Christoph) - Use i_cdev to pull struct nvme_ns in the ioctl path instead of populating file->private_data (from Christoph) - Change char device and sysfs entries to /dev/nvme-generic-XcYnZ to follow the hidden device naming scheme (from Christoph and Keith) Changes since V1: - Remove patches 1-3 which are already picked up by Christoph - Change the char device and sysfs entries to nvmeXnYc / c signals char device - Address Minwoo's comments on inline functions and style Javier González (1): nvme: enable char device per namespace Minwoo Im (1): nvme: allow open for nvme-generic char device drivers/nvme/host/core.c | 173 +++++++++++++++++++++++++++++++++++---- drivers/nvme/host/nvme.h | 9 ++ 2 files changed, 165 insertions(+), 17 deletions(-) -- 2.17.1 _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-02-22 19:02 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-22 19:01 javier [this message] 2021-02-22 19:01 ` [PATCH V5 0/2] nvme: enable char device per namespace javier 2021-02-22 19:01 ` [PATCH V5 1/2] " javier 2021-02-22 19:01 ` javier 2021-02-24 16:44 ` Christoph Hellwig 2021-02-24 16:44 ` Christoph Hellwig 2021-02-24 20:28 ` Javier González 2021-02-24 20:28 ` Javier González 2021-02-22 19:01 ` [PATCH V5 2/2] nvme: allow open for nvme-generic char device javier 2021-02-22 19:01 ` javier 2021-02-24 16:45 ` Christoph Hellwig 2021-02-24 16:45 ` Christoph Hellwig 2021-02-24 18:44 ` Minwoo Im 2021-02-24 18:44 ` 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=20210222190107.8479-1-javier.gonz@samsung.com \ --to=javier@javigon.com \ --cc=hch@lst.de \ --cc=javier.gonz@samsung.com \ --cc=kbusch@kernel.org \ --cc=linux-block@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ --cc=minwoo.im.dev@gmail.com \ --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: 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.