mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] regmap: maple: Implement block sync for the maple tree cache
Date: Mon, 12 Jun 2023 18:15:40 +0100	[thread overview]
Message-ID: <168659014071.85655.7107903749952317283.b4-ty@kernel.org> (raw)
In-Reply-To: <20230609-regcache-maple-sync-raw-v1-1-8ddeb4e2b9ab@kernel.org>

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


      reply	other threads:[~2023-06-12 17:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-11 12:06 Mark Brown
2023-06-12 17:15 ` Mark Brown [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=168659014071.85655.7107903749952317283.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®