From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] ARM: Broadcom Brahma-B15 readahead cache support
Date: Fri, 14 Jul 2017 15:11:11 -0700 [thread overview]
Message-ID: <23e2f72f-bc22-2084-660f-bc793e68c174@gmail.com> (raw)
In-Reply-To: <20170623175227.19743-1-f.fainelli@gmail.com>
On 06/23/2017 10:52 AM, Florian Fainelli wrote:
> Hi all,
>
> This patch series adds support for the Broadcom Brahma-B15 readahead cache.
> I submitted that patch series a couple of years ago, and then slept on it so
> here is another stab at it.
>
> Note that we did not implement this cache as a version of an outer cache
> for several reasons:
>
> - we initially thought we needed to intercept flush_icache_all and
> flush_kern_cache_louis but upon further inspection we convinced ourselves
> this is no longer needed, still, flush_cache_all() needs special handling
> here and needs to be wrapped around
>
> - the outer cache does not allow differentiating a DMA transfer direction
> this is a readahead cache, so it does not participate in writes, flushing
> it during reads *and* writes kills the performance completely
>
> - finally, most operations that outer_cache cares about are on MVA, which
> is transparent to the readahead cache here
>
> Changes in v2:
>
> - clarify that the read-ahead caches does invalidates on writes (IOW) based
> on Russell's feedback
Any comments on this? Thank you.
>
> Florian Fainelli (7):
> ARM: v7: allow setting different cache functions
> ARM: Add Broadcom Brahma-B15 readahead cache support
> ARM: Hook B15 readahead cache functions based on processor
> ARM: B15: Add CPU hotplug awareness
> ARM: B15: Add suspend/resume hooks
> ARM: B15: Register reboot notifier for KEXEC
> MAINTAINERS: Update brcmstb entries to cover B15 code
>
> MAINTAINERS | 2 +
> arch/arm/include/asm/glue-cache.h | 4 +
> arch/arm/include/asm/hardware/cache-b15-rac.h | 10 +
> arch/arm/mm/Kconfig | 8 +
> arch/arm/mm/Makefile | 1 +
> arch/arm/mm/cache-b15-rac.c | 360 ++++++++++++++++++++++++++
> arch/arm/mm/cache-v7.S | 21 ++
> arch/arm/mm/proc-v7.S | 6 +-
> include/linux/cpuhotplug.h | 2 +
> 9 files changed, 411 insertions(+), 3 deletions(-)
> create mode 100644 arch/arm/include/asm/hardware/cache-b15-rac.h
> create mode 100644 arch/arm/mm/cache-b15-rac.c
>
--
Florian
next prev parent reply other threads:[~2017-07-14 22:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 17:52 [PATCH v2 0/7] ARM: Broadcom Brahma-B15 readahead cache support Florian Fainelli
2017-06-23 17:52 ` [PATCH v2 1/7] ARM: v7: allow setting different cache functions Florian Fainelli
2017-06-23 17:52 ` [PATCH v2 2/7] ARM: Add Broadcom Brahma-B15 readahead cache support Florian Fainelli
2017-06-23 17:52 ` [PATCH v2 3/7] ARM: Hook B15 readahead cache functions based on processor Florian Fainelli
2017-06-23 17:52 ` [PATCH v2 4/7] ARM: B15: Add CPU hotplug awareness Florian Fainelli
2017-06-23 17:52 ` [PATCH v2 5/7] ARM: B15: Add suspend/resume hooks Florian Fainelli
2017-06-23 17:52 ` [PATCH v2 6/7] ARM: B15: Register reboot notifier for KEXEC Florian Fainelli
2017-06-23 17:52 ` [PATCH v2 7/7] MAINTAINERS: Update brcmstb entries to cover B15 code Florian Fainelli
2017-07-14 22:11 ` Florian Fainelli [this message]
2017-08-14 16:23 ` [PATCH v2 0/7] ARM: Broadcom Brahma-B15 readahead cache support Florian Fainelli
2017-12-01 0:17 ` Florian Fainelli
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=23e2f72f-bc22-2084-660f-bc793e68c174@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).