From: linus.walleij@stericsson•com (Linus Walleij)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: add clean and flush_dcache_all to ARM cache API
Date: Fri, 5 Nov 2010 16:22:43 +0100 [thread overview]
Message-ID: <4CD42143.50405@stericsson.com> (raw)
In-Reply-To: <20101105150813.GA25109@n2100.arm.linux.org.uk>
Russell King - ARM Linux wrote:
> On Fri, Nov 05, 2010 at 04:01:47PM +0100, Linus Walleij wrote:
>> This patch adds functions to flush and clean the entire data cache.
>> Since the existing flush/clean range functions take more time to
>> flush/clean the entire data cache, they cannot be used in
>> performance-critical situations:
>
> This is something that should be decided (as we already do for some
> processors) inside those methods. There's no need for new methods.
Aha so we should check the size of the buffer in the normal
cache clean_range/flush_range operations and if it exceeds a
certain watermark that we know for this specific arch we
clean/flush all cache instead?
Sounds like it could be done if I get it right.
Yours,
Linus Walleij
prev parent reply other threads:[~2010-11-05 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 15:01 [PATCH] ARM: add clean and flush_dcache_all to ARM cache API Linus Walleij
2010-11-05 15:08 ` Russell King - ARM Linux
2010-11-05 15:22 ` Linus Walleij [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=4CD42143.50405@stericsson.com \
--to=linus.walleij@stericsson$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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