From: John Meneghini <jmeneghi@redhat.com>
To: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Maurizio Lombardi <mlombard@redhat.com>,
Chris Leech <cleech@redhat.com>, Ewan Milne <emilne@redhat.com>
Subject: [LSF/MM/BPF TOPIC] NVMe Cancel support
Date: Thu, 20 Mar 2025 21:39:46 -0400 [thread overview]
Message-ID: <ec9b97de-68d2-43d4-9f76-65d4be91d49d@redhat.com> (raw)
I am scheduled to present on the topic of NVMe Cancel support next week in the LSF/MM/BPF IO Track.
Here's an abstract for my talk.
The NVMe Cancel command was added to the NVMe spec with TP4097a back in the NVMe 2.0 time frame[1].
At that time I was working for a storage array company and was personally involved with the
effort to add support for this protocol into the storage array's controller.
After moving to Red Hat in the fall of 2021 I started working with my engineering
team at Red Hat to add support for TP4097a to the Linux host.
My talk next week will present the latest version of Red Hat's patches - which are based upon
our previous versions[2] submitted for comments - and discuss some of the obstacles
and challenges we've encountered during implementation.
Almost all of these obstacles have to do with testing. We've had these patches working in our
lab for more than a year now, and we are happily able to send Cancel commands to the storage
array with no problems. However, these tests are not sufficient for upstream acceptance and we've
spent the last few months developing the nvmet patches needed to sufficiently test this feature
with a nvmet soft target..
I want to share those nvmet patches with the community and discuss what the possible next steps
could be to get this feature accepted upstream.
Many thanks to Chris Leech <cleech@redhat.com> and Maurizio Lombardi <mlombard@redhat.com> who
have done the lions share of this work.
[1] https://people.redhat.com/jmeneghi/LSFMM_2025/TP4097a_Abort_Enhancements_2021.07.26-Ratified.pdf
[2] https://lore.kernel.org/linux-nvme/20240912081510.171857-1-mlombard@redhat.com/
--
John A. Meneghini
Senior Principal Platform Storage Engineer
RHEL SST - Platform Storage Group
jmeneghi@redhat.com
reply other threads:[~2025-03-21 1:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ec9b97de-68d2-43d4-9f76-65d4be91d49d@redhat.com \
--to=jmeneghi@redhat.com \
--cc=cleech@redhat.com \
--cc=emilne@redhat.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@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