From: Jason Gunthorpe <jgg@nvidia.com>
To: Will Deacon <will@kernel.org>
Cc: Nicolin Chen <nicolinc@nvidia.com>,
Kiryl Shutsemau <kas@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>,
Pranjal Shrivastava <praan@google.com>,
Breno Leitao <leitao@debian.org>, 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 v3] iommu/arm-smmu-v3: Shrink command/event/PRI queues in kdump kernel
Date: Thu, 6 Aug 2026 12:58:55 -0300 [thread overview]
Message-ID: <20260806155855.GB71449@nvidia.com> (raw)
In-Reply-To: <anSFbIHnigVt_3bJ@willie-the-truck>
On Thu, Aug 06, 2026 at 02:00:28PM +0100, Will Deacon wrote:
> I probably wouldn't make a size of 0 disable the queue, either. Have a
> minimum size of a page or something like that.
If there is an argument someone is pressed for memory on cmdq they
probably also want to disable the fault queue (and fault support
entirely) and shrink the event queue too.
The kdump case was an obvious one, but I imagine an embedded system
may want similar tuning.
The non-disable-able ones should min to page size..
Jason
prev parent reply other threads:[~2026-08-06 15:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 8:47 Kiryl Shutsemau (Meta)
2026-07-15 11:46 ` Kiryl Shutsemau
2026-07-27 9:30 ` Kiryl Shutsemau
2026-07-28 10:16 ` Will Deacon
2026-07-28 13:53 ` Kiryl Shutsemau
2026-08-04 14:02 ` Will Deacon
2026-08-04 14:17 ` Jason Gunthorpe
2026-08-04 15:23 ` Robin Murphy
2026-08-04 16:04 ` Nicolin Chen
2026-08-04 16:19 ` Jason Gunthorpe
2026-08-04 16:45 ` Nicolin Chen
2026-08-04 16:59 ` Jason Gunthorpe
2026-08-04 17:39 ` Nicolin Chen
2026-08-06 13:00 ` Will Deacon
2026-08-06 15:58 ` Jason Gunthorpe [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=20260806155855.GB71449@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jkkm@meta.com \
--cc=joro@8bytes.org \
--cc=kas@kernel.org \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=praan@google.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
Powered by JetHome