From: Jason Gunthorpe <jgg@nvidia.com>
To: Kiryl Shutsemau <kas@kernel.org>
Cc: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>,
Nicolin Chen <nicolinc@nvidia.com>,
Pranjal Shrivastava <praan@google.com>,
Mostafa Saleh <smostafa@google.com>,
Thierry Reding <thierry.reding@kernel.org>,
Krishna Reddy <vdumpa@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Breno Leitao <leitao@debian.org>, Kyle McMartin <jkkm@meta.com>,
Usama Arif <usama.arif@linux.dev>,
kernel-team@meta.com, linux-arm-kernel@lists.infradead.org,
iommu@lists.linux.dev, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/2] iommu/arm-smmu-v3: Add a cmdq_max_n_shift module parameter
Date: Fri, 25 Sep 2026 09:46:45 -0300 [thread overview]
Message-ID: <20260925124645.GK9354@nvidia.com> (raw)
In-Reply-To: <arZFDAofKaurSjCd@thinkstation>
On Fri, Sep 25, 2026 at 11:01:31AM +0100, Kiryl Shutsemau wrote:
> On Wed, Sep 23, 2026 at 02:03:36PM -0300, Jason Gunthorpe wrote:
> > > [ ... 34 lines skipped ... ]
> > > @@ -40,6 +40,11 @@ module_param(disable_msipolling, bool, 0444);
> > > MODULE_PARM_DESC(disable_msipolling,
> > > "Disable MSI-based polling for CMD_SYNC completion.");
> > >
> > > +static unsigned int cmdq_max_n_shift;
> > > +module_param(cmdq_max_n_shift, uint, 0444);
> > > +MODULE_PARM_DESC(cmdq_max_n_shift,
> > > + "Cap on the command queue depth, as log2 of the number of entries. Zero means the hardware maximum; the queue never shrinks below one page.");
> >
> > The patch looks ok
> >
> > Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
> >
> > But I'd rather use lg2 as name, especially user visible, instead of
> > n_shift. "shift" is a word for bitwise stuff, this is a 2**N log2
> > encoded value.
>
> This name has changed twice already. v5 took the value in entries.
> Nicolin asked for a log2 value and named it after max_n_shift, which is
> what the driver calls this quantity everywhere else.
>
> I would rather not rename it a third time without input from the
> maintainer.
>
> Will, this is the user-visible name. Do you have a preference here?
> Unless you want it changed I will leave v6 as it is.
Please at least fix the internal logic to work in the saner way I
showed
Jason
next prev parent reply other threads:[~2026-09-25 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 9:52 [PATCH v6 0/2] iommu/arm-smmu-v3: Make the queue depths tunable, and shrink them in a kdump kernel Kiryl Shutsemau (Meta)
2026-09-09 9:52 ` [PATCH v6 1/2] iommu/arm-smmu-v3: Add a cmdq_max_n_shift module parameter Kiryl Shutsemau (Meta)
2026-09-15 12:16 ` Breno Leitao
2026-09-23 17:03 ` Jason Gunthorpe
2026-09-25 10:01 ` Kiryl Shutsemau
2026-09-25 12:46 ` Jason Gunthorpe [this message]
2026-09-09 9:52 ` [PATCH v6 2/2] iommu/arm-smmu-v3: Default queue depths to one page in a kdump kernel Kiryl Shutsemau (Meta)
2026-09-15 11:20 ` Yuanhe Shu
2026-09-23 17:03 ` Jason Gunthorpe
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=20260925124645.GK9354@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jkkm@meta.com \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=kas@kernel.org \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=praan@google.com \
--cc=robin.murphy@arm.com \
--cc=smostafa@google.com \
--cc=thierry.reding@kernel.org \
--cc=usama.arif@linux.dev \
--cc=vdumpa@nvidia.com \
--cc=will@kernel.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
all inboxes | Powered by JetHome®