From: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
To: "Dan Malek" <dan@embeddededge.com>
Cc: "Linuxppc-Embedded@Lists. Linuxppc. Org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Improved copy_page() function, about 30% speed up for mpc860!
Date: Tue, 4 Mar 2003 01:09:12 +0100 [thread overview]
Message-ID: <007a01c2e1e2$493c43e0$020120b0@jockeXP> (raw)
In-Reply-To: 3E63C905.5000306@embeddededge.com
> Joakim Tjernlund wrote:
>
> > I have been playing with the copy_page() function in arch/ppc/kernel/misc.S
> > and gained about 30% speed up for my mpc860, rev D4 MHz.
>
> Have you found the discussion in linuxppc-dev about the work Paul has done
> on this in general for PowerPC? It may help avoid repeating some work and
> provide some guidance.....
I have searched but I did not find anything conclusive. Pointers?
> And don't forget....many applications aren't heavily 'copy-centric' and it
> may be beneficial to not blow away the caches in those cases. That is, if
If you are referring to the copy_page() that I attached in my first mail, then
yes it uses more icache, but if you have seen my later post where I took it
back and stated that just enabling dcbz in the existing version of copy_page()
would give the same speed up, I don't follow you. How am I wasting caches?
In the end I would like to modify copy_tofrom_user() so that dcbz is used on kernel space
addresses but not on user space without adding a lot of code. Ideas welcome.
> you apply systems engineering methods to your testing instead of just focusing
> on such a low level detail, you may discover you are wasting your time and
> from an overall system application you may be providing little benefit or
> even a overall degradation in system performance.
I am just trying make 8xx perform a little better and I focus on areas I know something
about such as crc32, the enet.c driver and in this case various memory copy stuff. Hopefully
the end result will be useful to me and others.
Jocke
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-04 0:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 13:08 Improved copy_page() function, about 30% speed up for mpc860! Joakim Tjernlund
2003-02-27 15:45 ` Joakim Tjernlund
2003-02-28 17:31 ` Joakim Tjernlund
2003-03-03 21:28 ` Dan Malek
2003-03-04 0:09 ` Joakim Tjernlund [this message]
2003-03-04 0:19 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2003-03-02 17:50 Joakim Tjernlund
2003-03-03 21:18 ` Dan Malek
2003-03-03 23:16 ` Joakim Tjernlund
2003-03-04 0:43 ` Dan Malek
2003-03-04 0:54 ` Daniel Jacobowitz
2003-03-04 3:38 ` Dan Malek
2003-03-04 8:29 ` Joakim Tjernlund
2003-03-04 13:33 ` Dan Malek
2003-03-04 15:24 ` Joakim Tjernlund
2003-03-04 17:00 ` Dan Malek
2003-03-04 22:01 ` Joakim Tjernlund
2003-03-04 22:41 ` Dan Malek
2003-03-04 23:20 ` Joakim Tjernlund
2003-03-04 23:35 ` Tom Rini
2003-03-04 23:45 ` Joakim Tjernlund
2003-03-05 0:05 ` Tom Rini
2003-03-05 0:19 ` Joakim Tjernlund
2003-03-05 17:12 ` Tom Rini
2003-03-05 17:50 ` Joakim Tjernlund
2003-03-05 17:15 ` Dan Malek
[not found] ` <1046737789.885.15.camel@zion.wanadoo.fr>
2003-03-04 0:51 ` Dan Malek
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='007a01c2e1e2$493c43e0$020120b0@jockeXP' \
--to=joakim.tjernlund@lumentis.se \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.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).