From: Randy Jennings <randyj@purestorage.com>
To: lsf-pc@lists.linux-foundation.org, linux-nvme@lists.infradead.org
Cc: cleech@redhat.com, mkhalfella@purestorage.com
Subject: [PATCH 0/7] NOT FOR MERGE nvmet code to exercise CCR/CQT
Date: Thu, 30 Apr 2026 17:29:06 -0600 [thread overview]
Message-ID: <20260430232913.129271-1-randyj@purestorage.com> (raw)
This code is not for check-in or as an RFC.
This post is just an FYI of code used on the target for
a functional test for CCR/CQT for this presentation:
https://lore.kernel.org/linux-nvme/CAPpK+O03nHvHGESXsDDARz_kgbNkmeHmu-G3XWto7CqHtyVedQ@mail.gmail.com/
The code by Chris Leech comes from the NVMe Cancel implemetation posted here:
https://lore.kernel.org/linux-nvme/20250324102310.658007-1-mlombard@redhat.com/
Code built on:
v3 of the CCR+CQT patches as described here:
https://lore.kernel.org/linux-nvme/20260214042753.4073668-1-mkhalfella@purestorage.com/T
* 011e0880d366 - nvmet: report NPDGL and NPDAL (8 weeks ago) <Caleb Sander Mateos>
(which was nvme-next a few weeks ago):
Chris Leech (3):
nvmet: put all nvmet_req.execute calls behind a function name
nvmet: add delay debugfs file to nvmet_ctrl
nvmet: delay requests
Mohamed Khalfella (4):
fixup: nvme fix CCR command
nvmet: Added debugfs fatal opcode
nvmet: kill nvme controller when fatal opcode is received
Force CCR operation to fail
drivers/nvme/target/Kconfig | 19 ++++++++
drivers/nvme/target/admin-cmd.c | 11 ++---
drivers/nvme/target/core.c | 37 ++++++++++++++++
drivers/nvme/target/debugfs.c | 78 +++++++++++++++++++++++++++++++++
drivers/nvme/target/fc.c | 4 +-
drivers/nvme/target/loop.c | 2 +-
drivers/nvme/target/nvmet.h | 17 +++++++
drivers/nvme/target/rdma.c | 4 +-
drivers/nvme/target/tcp.c | 4 +-
include/linux/nvme.h | 4 +-
10 files changed, 166 insertions(+), 14 deletions(-)
--
2.54.0
next reply other threads:[~2026-04-30 23:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 23:29 Randy Jennings [this message]
2026-04-30 23:29 ` [PATCH 1/7] fixup: nvme fix CCR command Randy Jennings
2026-04-30 23:29 ` [PATCH 2/7] nvmet: put all nvmet_req.execute calls behind a function name Randy Jennings
2026-04-30 23:29 ` [PATCH 3/7] nvmet: add delay debugfs file to nvmet_ctrl Randy Jennings
2026-04-30 23:29 ` [PATCH 4/7] nvmet: delay requests Randy Jennings
2026-04-30 23:29 ` [PATCH 5/7] nvmet: Added debugfs fatal opcode Randy Jennings
2026-04-30 23:29 ` [PATCH 6/7] nvmet: kill nvme controller when fatal opcode is received Randy Jennings
2026-04-30 23:29 ` [PATCH 7/7] Force CCR operation to fail Randy Jennings
2026-05-10 22:39 ` [PATCH 0/7] NOT FOR MERGE nvmet code to exercise CCR/CQT Sagi Grimberg
2026-05-11 19:14 ` Randy Jennings
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=20260430232913.129271-1-randyj@purestorage.com \
--to=randyj@purestorage.com \
--cc=cleech@redhat.com \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mkhalfella@purestorage.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