From: Hollis Blanchard <hollisb@us.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
xen-ppc-devel <xen-ppc-devel@lists.xensource.com>
Subject: Re: copy_4K_page() doesn't use dcbtst?
Date: Mon, 28 Aug 2006 21:11:53 -0500 [thread overview]
Message-ID: <1156817513.13497.12.camel@diesel> (raw)
In-Reply-To: <17651.34629.132793.190742@cargo.ozlabs.ibm.com>
On Tue, 2006-08-29 at 10:16 +1000, Paul Mackerras wrote:
> Hollis Blanchard writes:
>
> > Hi Paul, some Xen people were just noticing that copy_4K_page
> > (arch/powerpc/lib/copypage_64.S) doesn't use the dcbtst instruction. Why
> > doesn't it help there?
>
> Why would we want to read the cache lines for the destination from
> memory when we're only going to overwrite them completely anyway?
>
> A stronger argument would be for using dcbz, but IIRC it actually made
> things slower (on POWER4 at least). I suspect the hardware is
> gathering the stores for the whole of each cache line automatically,
> so using dcbz doesn't provide any benefit.
Yes, dcbz makes more sense.
> I did a lot of measurements of memory copy speed on POWER4 (using
> different copy loops, copy sizes, alignments, cache hot/cold cases)
> and the copy_4K_page loop is the fastest I could come up with for
> POWER4. If anyone can come up with a routine that is measurably
> faster on current machines, I'm happy to look at it, of course.
I figured you had done measurements; we were just curious about the
unexpected results. Thanks!
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2006-08-29 2:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 17:35 copy_4K_page() doesn't use dcbtst? Hollis Blanchard
2006-08-29 0:16 ` Paul Mackerras
2006-08-29 2:11 ` Hollis Blanchard [this message]
2006-08-29 6:57 ` Segher Boessenkool
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=1156817513.13497.12.camel@diesel \
--to=hollisb@us.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=xen-ppc-devel@lists.xensource.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).