public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: 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: Re: [LSF/MM?BFP TOPIC] Block-layer device resets
Date: Tue, 3 Feb 2026 11:14:13 +0800	[thread overview]
Message-ID: <aYFoBafih46bLK0T@fedora> (raw)
In-Reply-To: <50ee77fa-0c44-422e-9ee2-eece60b189e1@suse.de>

Hi Hannes,

On Sun, Feb 01, 2026 at 06:06:52PM +0100, Hannes Reinecke wrote:
> 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.

Can you provide a little background why this reset is required? And for
solve which problem?

> 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.

nvme_quiesce_io_queues() & nvme_cancel_tagset() may do it, or do you have
other new requirement not covered by the two helpers?


Thanks, 
Ming


  parent reply	other threads:[~2026-02-03  3:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-01 17:06 [LSF/MM?BFP TOPIC] Block-layer device resets Hannes Reinecke
2026-02-02  1:46 ` 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 [this message]
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=aYFoBafih46bLK0T@fedora \
    --to=ming.lei@redhat.com \
    --cc=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