From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from verein.lst.de (verein.lst.de [213.95.11.211])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by smtp.subspace.kernel.org (Postfix) with ESMTPS id 841024028FD
	for <linux-kernel@vger.kernel.org>; Wed, 27 May 2026 13:19:56 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.95.11.211
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1779887997; cv=none; b=iEUxffKW9sxwUQ51HmbSgE9K9+TpFmI6vaTwK3q9IntumHu+E/jtlbXxSO9pqcZ1O6rr1E4KzN9sAZMdyDr3rX0fE8ceZxYRUEwusqwW/+KqJlMrhsyZjzSdeHDHqpHwI2vWUj33PZkxHfTW5ao7ylY/HcelWeIhIS0opFk9hsc=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1779887997; c=relaxed/simple;
	bh=ruVBWkmzyKsG4yn91qWaNnVEicu673drHN9bupPHBP0=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=oyU6ILlQL5P6aARoGB6IycJaHgn7ujqJiTD5+RRmon632EOybYQ6/jSQOrCP5WIHGsW6dopx9yco5bVWzrWIzi/f1jfEkG4N+DhbGurKm6U08s1PPZ9FW8dFGK+nSkV2KOm2pcfdhB0nLqYKZKId7QZgyDWf5s4QFohMi/9JPbA=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de; spf=pass smtp.mailfrom=lst.de; arc=none smtp.client-ip=213.95.11.211
Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de
Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lst.de
Received: by verein.lst.de (Postfix, from userid 2407)
	id CFA0F68B05; Wed, 27 May 2026 15:19:51 +0200 (CEST)
Date: Wed, 27 May 2026 15:19:51 +0200
From: Christoph Hellwig <hch@lst.de>
To: guzebing <guzebing1612@gmail.com>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	Guzebing <guzebing@bytedance.com>
Subject: Re: [RFC PATCH 0/1] nvme-pci: detect I/O queue depth changes after
 reset
Message-ID: <20260527131951.GA11071@lst.de>
References: <20260527075320.3178600-1-guzebing1612@gmail.com>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20260527075320.3178600-1-guzebing1612@gmail.com>
User-Agent: Mutt/1.5.17 (2007-11-01)

On Wed, May 27, 2026 at 03:53:19PM +0800, guzebing wrote:
> This RFC instead takes the smaller approach of detecting the reset-time
> CAP.MQES change and making it visible.  If the live I/O queue depth
> shrinks, reset recovery is failed before recreating I/O queues.  If it
> grows, the driver warns and continues with the existing queue resources.

Unlike the other version this at least sounds doable without creating
a complete mess.  So if we can live with this version that'd make me
much happier.