lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ca528e3e-39f1-41cc-9f46-ad787af48a77@sirena.org.uk>
Date: Thu, 16 Oct 2025 12:53:10 +0100
From: Mark Brown <broonie@...nel.org>
To: Sander Vanheule <sander@...nheule.net>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"Rafael J. Wysocki" <rafael@...nel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] regmap: add cache validity to REGCACHE_FLAT

On Thu, Oct 16, 2025 at 10:46:33AM +0200, Sander Vanheule wrote:

> Would you be open to providing a new type of flat cache with sparse
> initalisation (e.g. REGCACHE_FLAT_SPARSE) to provide the behavior provided by
> this patches? Most of the code could be shared with REGCACHE_FLAT.

Taking a step back for a minute, what's the actual problem you're trying
to solve here?  Why use a flat cache rather than a maple tree cache for
your application?

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ