From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: Re: powerpc/64s: Improve RFI L1-D cache flush fallback
Date: Mon, 29 Jan 2018 15:13:49 +1100 (AEDT) [thread overview]
Message-ID: <3zVGNF3ZPSz9t3k@ozlabs.org> (raw)
In-Reply-To: <20180117135818.10241-1-npiggin@gmail.com>
On Wed, 2018-01-17 at 13:58:18 UTC, Nicholas Piggin wrote:
> The fallback RFI flush is used when firmware does not provide a way
> to flush the cache. It's a "displacement flush" that evicts useful
> data by displacing it with an uninteresting buffer.
>
> The flush has to take care to work with implementation specific cache
> replacment policies, so the recipe has been in flux. The initial
> slow but conservative approach is to touch all lines of a congruence
> class, with dependencies between each load. It has since been
> determined that a linear pattern of loads without dependencies is
> sufficient, and is significantly faster.
>
> Measuring the speed of a null syscall with RFI fallback flush enabled
> gives the relative improvement:
>
> P8 - 1.83x
> P9 - 1.75x
>
> The flush also becomes simpler and more adaptable to different cache
> geometries.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/bdcb1aefc5b3f7d0f1dc8b02673602
cheers
prev parent reply other threads:[~2018-01-29 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 13:58 [PATCH] powerpc/64s: Improve RFI L1-D cache flush fallback Nicholas Piggin
2018-01-29 4:13 ` Michael Ellerman [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=3zVGNF3ZPSz9t3k@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
/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).