From: Hannes Reinecke <hare@suse.de>
To: lsf-pc <lsf-pc@lists.linux-foundation.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: [LSF/MM?BFP TOPIC] Block-layer device resets
Date: Sun, 1 Feb 2026 18:06:52 +0100 [thread overview]
Message-ID: <50ee77fa-0c44-422e-9ee2-eece60b189e1@suse.de> (raw)
Hi all,
We are currently working on implementing cross-controller resets for
NVMe, which requires to send a command to the target which then should
terminate all commands on a given controller.
While we could easily terminate the controller, the specification
also requires us to terminate all outstanding commands.
Which then recurses into my all-time favourite topic on how to
abort outstanding commands from the fs/bio layer.
However, here we don't have to dissect/match to individual commands,
but rather have to abort everything, which seems rather easier.s
So I would like to fathom whether such a thing is feasible/reasonable
(I think so, obviously, and can think of several other use-cases, too,
qemu springs to mind here ...) and discuss possible implementations
(set 'req->deadline' to zero for all pending commands?).
Or maybe we can do such a thing already and I'm just not aware of it...
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next reply other threads:[~2026-02-01 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 17:06 Hannes Reinecke [this message]
2026-02-02 1:46 ` [LSF/MM?BFP TOPIC] Block-layer device resets Damien Le Moal
2026-02-02 23:04 ` Hannes Reinecke
2026-02-03 12:19 ` Nilay Shroff
2026-02-04 1:43 ` Hannes Reinecke
2026-02-02 17:27 ` Bart Van Assche
2026-02-02 23:10 ` Hannes Reinecke
2026-02-03 3:14 ` Ming Lei
2026-02-03 5:51 ` [LSF/MM/BFP " Hannes Reinecke
2026-02-04 1:14 ` Ming Lei
2026-02-04 1:50 ` Hannes Reinecke
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=50ee77fa-0c44-422e-9ee2-eece60b189e1@suse.de \
--to=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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