[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220601051621.GA21535@lst.de>
Date: Wed, 1 Jun 2022 07:16:21 +0200
From: Christoph Hellwig <hch@....de>
To: Rob Clark <robdclark@...il.com>
Cc: Robin Murphy <robin.murphy@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
Rob Clark <robdclark@...omium.org>,
Christoph Hellwig <hch@....de>,
Marek Szyprowski <m.szyprowski@...sung.com>,
"open list:DMA MAPPING HELPERS" <iommu@...ts.linux-foundation.org>
Subject: Re: [PATCH] dma-debug: Make things less spammy under memory
pressure
On Tue, May 31, 2022 at 03:19:45PM -0700, Rob Clark wrote:
> um, quite.. tbf that was in the context of a WIP igt test for
> shrinker which was trying to cycle thru ~2x RAM size worth of GEM
> buffers on something like 72 threads. So it could just be threads
> that had gotten past the dma_debug_disabled() check already before
> global_disable was set to true?
>
> I guess this could be pr_err_once() instead, then?
Yes, we could use pr_err_once to reduce the chattyness while still
keeping global_disable to disable all the actual tracking.
Powered by blists - more mailing lists