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 D92562E62D9
	for <linux-kernel@vger.kernel.org>; Wed,  1 Apr 2026 14:10:37 +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=1775052639; cv=none; b=TZaFBXkL1X3rmzzgN6SCVHRr8OtFktE+b4QN8eFLLDuxDigKZ6LACI22UKES0HHkiYUX2eWFb4gpXM2l6rkzo+QFxbhTWRClLc+dQtq/7TFXjAj0/rPZcWnf3RzCm2L+ZSX/AAvnvvK+3vUNRW9vazHifVQk06eJTkVDm9DhEtM=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1775052639; c=relaxed/simple;
	bh=3M1/Tkm8u9tQZjqB+dsOOzWMTBVkKfXjeRtZ7k/iZQs=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=Wu+HhmmIHW/9eP+TOhPqxltCkgJUjKV466rfpvr++1qTx5f3t0QNZv9mL/nZWkYF/qOZ0RQPlAxB4L8dlD1e/noHuSJE67WlevktAyGjsOF7Ja7vp60ve1VM3Hz4sd7/OTpqmrCzxW38xTtzJwsXzndvqwN2yGH9RoJPso3lblI=
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 84FDE68C4E; Wed,  1 Apr 2026 16:10:35 +0200 (CEST)
Date: Wed, 1 Apr 2026 16:10:35 +0200
From: Christoph Hellwig <hch@lst.de>
To: Aurelien Aptel <aaptel@nvidia.com>
Cc: linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
	Sagi Grimberg <sagi@grimberg.me>,
	Chaitanya Kulkarni <kch@nvidia.com>, smalin@nvidia.com,
	linux-kernel@vger.kernel.org, Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: Re: [PATCH] nvmet: introduce new mdts configuration entry
Message-ID: <20260401141035.GE21703@lst.de>
References: <20260401101355.163294-1-aaptel@nvidia.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: <20260401101355.163294-1-aaptel@nvidia.com>
User-Agent: Mutt/1.5.17 (2007-11-01)

On Wed, Apr 01, 2026 at 10:13:55AM +0000, Aurelien Aptel wrote:
> Using this port configuration, one will be able to set the Maximum Data
> Transfer Size (MDTS) for any controller that will be associated to the
> configured port.
> 
> The default value stayed 0 (no limit) but each transport will be able to
> set its own values before enabling the port.

The ZASL calculation in zns.c also needs to take this limit into account.
So maybe add a helper to calculate it?