[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZcIE/RMTq34TgpQt@finisterre.sirena.org.uk>
Date: Tue, 6 Feb 2024 10:07:57 +0000
From: Mark Brown <broonie@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Bo Liu <liubo03@...pur.com>, lee@...nel.org, wens@...e.org,
marek.vasut+renesas@...il.com, support.opensource@...semi.com,
neil.armstrong@...aro.org, ckeepax@...nsource.cirrus.com,
rf@...nsource.cirrus.com, mazziesaccount@...il.com,
mcoquelin.stm32@...il.com, alexandre.torgue@...s.st.com,
linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
linux-amlogic@...ts.infradead.org, patches@...nsource.cirrus.com,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 00/18] mfd: convert to use maple tree register cache
On Tue, Feb 06, 2024 at 10:33:22AM +0100, Geert Uytterhoeven wrote:
> If all of this is true, is there any reason to keep REGCACHE_RBTREE
> around? If not, perhaps REGCACHE_RBTREE should be treated as
> REGCACHE_MAPLE in the regmap core code first, followed by a single
> tree-wide patch to replace REGCACHE_RBTREE?
There is a very small niche for devices where cache syncs are a
particularly important part of the workload where rbtree's choices might
give better performance, especially on systems with low end CPUs.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists