From: Kanchan Joshi <joshiiitr@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Minwoo Im <minwoo.im.dev@gmail.com>,
Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
"Javier Gonz??lez" <javier.gonz@samsung.com>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: introduce generic per-namespace chardev
Date: Tue, 20 Apr 2021 23:43:51 +0530 [thread overview]
Message-ID: <CA+1E3rLB5C+zP1xduzwq2uwWgEWFxUt5x=hostq5YOgj_QBNbA@mail.gmail.com> (raw)
In-Reply-To: <20210420100746.2801722-2-hch@lst.de>
On Tue, Apr 20, 2021 at 3:37 PM Christoph Hellwig <hch@lst.de> wrote:
>
> From: Minwoo Im <minwoo.im.dev@gmail.com>
>
> Userspace has not been allowed to I/O to device that's failed to
> be initialized. This patch introduces generic per-namespace character
> device to allow userspace to I/O regardless the block device is there or
> not.
When an application uses this interface to issue passthrough IO, it
needs to know the lba size (at least) to form the command correctly.
But determining lba size would require an admin ioctl.
Do you see there is a way to go about this issue?
--
Joshi
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-04-20 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 10:07 nvme generic per-namespace char device Christoph Hellwig
2021-04-20 10:07 ` [PATCH] nvme: introduce generic per-namespace chardev Christoph Hellwig
2021-04-20 18:13 ` Kanchan Joshi [this message]
2021-04-20 18:58 ` Keith Busch
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='CA+1E3rLB5C+zP1xduzwq2uwWgEWFxUt5x=hostq5YOgj_QBNbA@mail.gmail.com' \
--to=joshiiitr@gmail.com \
--cc=hch@lst.de \
--cc=javier.gonz@samsung.com \
--cc=kbusch@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: 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).