From: Breno Leitao <leitao@debian.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: "Kiryl Shutsemau (Meta)" <kas@kernel.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>,
Nicolin Chen <nicolinc@nvidia.com>,
Kyle McMartin <jkkm@meta.com>, Usama Arif <usama.arif@linux.dev>,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/arm-smmu-v3: Shrink command/event/PRI queues in kdump kernel
Date: Thu, 2 Jul 2026 01:24:05 -0700 [thread overview]
Message-ID: <akYf9JXqAakxJEHF@gmail.com> (raw)
In-Reply-To: <20260702001603.GN7525@ziepe.ca>
On Wed, Jul 01, 2026 at 09:16:03PM -0300, Jason Gunthorpe wrote:
> On Wed, Jul 01, 2026 at 04:45:28PM +0100, Kiryl Shutsemau (Meta) wrote:
> > The command, event and PRI queues are sized from the maxima the hardware
> > advertises in IDR1, which can be several megabytes each. On systems with
> > many SMMUv3 instances that cost is paid per instance and adds up to tens
> > of megabytes of coherent DMA in the capture kernel.
> >
> > A kdump capture kernel runs from a small crashkernel reservation and only
> > has to drive the few devices used to save the dump, so deep queues serve
> > no purpose. The queues carry invalidation commands and fault records, not
> > DMA data, so dump throughput is unaffected; a shallower queue only bounds
> > how many commands may be in flight before a sync, which does not matter for
> > the capture kernel's small device count and modest I/O.
> >
> > Clamp every queue to a single page when is_kdump_kernel() is true. Doing
> > it in arm_smmu_init_one_queue() covers the command, event and PRI queues
> > in one place. The command queue still holds at least one batch plus a sync
> > (256 entries on a 4K-page kernel, well above CMDQ_BATCH_ENTRIES), so
> > command batching keeps working.
> >
> > Suggested-by: Kyle McMartin <jkkm@meta.com>
> > Signed-off-by: Kiryl Shutsemau (Meta) <kas@kernel.org>
> > ---
> > drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
>
> Make sense to me
>
> > + if (is_kdump_kernel()) {
> > + u32 ent_sz_shift = ilog2(dwords) + 3;
> > +
> > + q->llq.max_n_shift = min_t(u32, q->llq.max_n_shift,
> > + PAGE_SHIFT - ent_sz_shift);
>
> I saw lately many people saying you should not use min_t, why is it
> needed here?
Good point, it seems that both of them are u32
- q->llq.max_n_shift is u32 (struct arm_smmu_ll_queue)
- ent_sz_shift is u32, and PAGE_SHIFT is a small int constant, so
PAGE_SHIFT - ent_sz_shift promotes to u32 too.
min() should be enough, I would say. With that, please feel free to add:
Reviewed-by: Breno Leitao <leitao@debian.org>
prev parent reply other threads:[~2026-07-02 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 15:45 [PATCH] iommu/arm-smmu-v3: Shrink command/event/PRI queues in kdump kernel Kiryl Shutsemau (Meta)
2026-07-02 0:16 ` Jason Gunthorpe
2026-07-02 8:24 ` Breno Leitao [this message]
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=akYf9JXqAakxJEHF@gmail.com \
--to=leitao@debian.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=jkkm@meta.com \
--cc=joro@8bytes.org \
--cc=kas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=usama.arif@linux.dev \
--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