[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPpK+O0LDYrrErxkGDQ6fF-hP2mUNPHXKm5B=w-Fua_Gjb6g2w@mail.gmail.com>
Date: Thu, 18 Dec 2025 17:39:07 -0800
From: Randy Jennings <randyj@...estorage.com>
To: Mohamed Khalfella <mkhalfella@...estorage.com>
Cc: Chaitanya Kulkarni <kch@...dia.com>, Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...nel.dk>,
Keith Busch <kbusch@...nel.org>, Sagi Grimberg <sagi@...mberg.me>,
Aaron Dailey <adailey@...estorage.com>, John Meneghini <jmeneghi@...hat.com>,
Hannes Reinecke <hare@...e.de>, linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 07/14] nvme: Add RECOVERING nvme controller state
On Thu, Dec 18, 2025 at 3:18 PM Randy Jennings <randyj@...estorage.com> wrote:
>
> On Tue, Nov 25, 2025 at 6:13 PM Mohamed Khalfella
> <mkhalfella@...estorage.com> wrote:
> >
> > Reset codepath takes care of queues teardown and inflight requests
> > cancellation.
Note: Tearing down the connection (with the queues) after going through
CCR-based recovery or time-based recovery is late. CCR will trigger a
disconnect on the host side, and, because we stop traffic to the nvme
controller, KATO should kick in if CCR does not, so I accept your
argument that tearing down the connections first could be considered
an optimization that can get implemented later.
Sincerely,
Randy Jennings
Powered by blists - more mailing lists