From: Clay Mayers <Clay.Mayers@kioxia.com>
To: Kanchan Joshi <joshi.k@samsung.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>, "hch@lst.de" <hch@lst.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"ming.lei@redhat.com" <ming.lei@redhat.com>
Subject: RE: [LSF/MM/BPF ATTEND][LSF/MM/BPF Topic] Non-block IO
Date: Fri, 10 Feb 2023 20:07:09 +0000 [thread overview]
Message-ID: <65b5a06a163246e293a0452c03a59a2b@kioxia.com> (raw)
In-Reply-To: <20230210180033.321377-1-joshi.k@samsung.com>
> From Kanchan Joshi
> Sent: Friday, February 10, 2023 10:01 AM
> To: lsf-pc@lists.linux-foundation.org
> Cc: linux-block@vger.kernel.org; linux-nvme@lists.infradead.org; io-
> uring@vger.kernel.org; axboe@kernel.dk; hch@lst.de; kbusch@kernel.org;
> ming.lei@redhat.com; Kanchan Joshi <joshi.k@samsung.com>
> Subject: [LSF/MM/BPF ATTEND][LSF/MM/BPF Topic] Non-block IO
>
> is getting more common than it used to be.
> NVMe is no longer tied to block storage. Command sets in NVMe 2.0 spec
> opened an excellent way to present non-block interfaces to the Host. ZNS
> and KV came along with it, and some new command sets are emerging.
Some command sets require features of NVMe the kernel doesn't support;
fused and some AENs for example. It would be very useful to work with
non-block command sets w/o modifying the NVMe driver, having a custom
NVMe driver per command set or resorting to using spdk.
next prev parent reply other threads:[~2023-02-10 20:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230210180226epcas5p1bd2e1150de067f8af61de2bbf571594d@epcas5p1.samsung.com>
2023-02-10 18:00 ` [LSF/MM/BPF ATTEND][LSF/MM/BPF Topic] Non-block IO Kanchan Joshi
2023-02-10 18:18 ` Bart Van Assche
2023-02-10 19:34 ` Kanchan Joshi
2023-02-13 20:24 ` Bart Van Assche
2023-02-10 19:47 ` Jens Axboe
2023-02-14 10:33 ` John Garry
2023-02-10 19:53 ` Jens Axboe
2023-02-13 11:54 ` Sagi Grimberg
2023-04-11 22:48 ` Kanchan Joshi
2023-04-11 22:53 ` Jens Axboe
2023-04-11 23:28 ` Kanchan Joshi
2023-04-12 2:12 ` Jens Axboe
2023-04-12 2:33 ` Ming Lei
2023-04-12 13:26 ` Kanchan Joshi
2023-04-12 13:47 ` Ming Lei
2023-02-10 20:07 ` Clay Mayers [this message]
2023-02-11 3:33 ` Ming Lei
2023-02-11 12:06 ` Hannes Reinecke
2023-02-28 16:05 ` John Meneghini
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=65b5a06a163246e293a0452c03a59a2b@kioxia.com \
--to=clay.mayers@kioxia.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=io-uring@vger.kernel.org \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=ming.lei@redhat.com \
/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