From: John Meneghini <jmeneghi@redhat.com>
To: Kanchan Joshi <joshi.k@samsung.com>, 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
Subject: Re: [LSF/MM/BPF ATTEND][LSF/MM/BPF Topic] Non-block IO
Date: Tue, 28 Feb 2023 11:05:07 -0500 [thread overview]
Message-ID: <d72e3ef4-f607-9a63-9f6d-b03084a8edf6@redhat.com> (raw)
In-Reply-To: <20230210180033.321377-1-joshi.k@samsung.com>
On 2/10/23 13:00, Kanchan Joshi wrote:
> 1. Command cancellation: while NVMe mandatorily supports the abort
> command, we do not have a way to trigger that from user-space. There
> are ways to go about it (with or without the uring-cancel interface) but
> not without certain tradeoffs. It will be good to discuss the choices in
> person.
As one of the principle authors of TP4097a and the author of the one NVMe controller implementation that supports the NVMe
Cancel command I would like to attend LSF/MM this year and talk about this.
See my SDC presentation where I describe all of the problems with the NVMe Abort command and demonstrates a Linux host sending
NVMe Abort and Cancel command to an IO controller:
https://www.youtube.com/watch?v=vRrAD1U0IRw
/John
prev parent reply other threads:[~2023-02-28 16:05 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
2023-02-11 3:33 ` Ming Lei
2023-02-11 12:06 ` Hannes Reinecke
2023-02-28 16:05 ` John Meneghini [this message]
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=d72e3ef4-f607-9a63-9f6d-b03084a8edf6@redhat.com \
--to=jmeneghi@redhat.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;
as well as URLs for NNTP newsgroup(s).