linux-kernel - Re: [PATCH] regmap: maple: Implement block sync for the maple tree cache

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] [day] [month] [year] [list]

Message-Id: <168659014071.85655.7107903749952317283.b4-ty@kernel.org>
Date:   Mon, 12 Jun 2023 18:15:40 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH] regmap: maple: Implement block sync for the maple tree
 cache

On Sun, 11 Jun 2023 13:06:07 +0100, Mark Brown wrote:
> For register maps where we can write multiple values in a single bus
> operation it is generally much faster to do so. Improve the performance of
> maple tree cache syncs on such devices by identifying blocks of adjacent
> registers that need to be written out and combining them into a single
> operation.
> 
> Combining writes does mean that we need to allocate a scratch buffer and
> format the data into it but it is expected that for most cases where caches
> are in use the cost of I/O will be much greater than the cost of doing the
> allocation and format.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/1] regmap: maple: Implement block sync for the maple tree cache
      commit: bfa0b38c148379c8a8c52e23bbdcb086414fb354

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark