From: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
To: "Dan Malek" <dan@embeddededge.com>
Cc: <linuxppc-dev@lists.linuxppc.org>, <drow@false.org>
Subject: Re: Improved copy_page() function, about 30% speed up for mpc860!
Date: Tue, 4 Mar 2003 00:16:10 +0100 [thread overview]
Message-ID: <006a01c2e1da$e108ddd0$020120b0@jockeXP> (raw)
In-Reply-To: 3E63C6BE.6020002@embeddededge.com
> Joakim Tjernlund wrote:
>
> > I found a link that may have relevance regarding the dcbz problem , can anybody confirm this?
> > http://www.uwsg.iu.edu/hypermail/linux/kernel/0012.0/0529.html
>
> This is just one of the many different things that happen with various
> silicon versions and the use of the cache instructions on the 8xx.
> In this particular case, we have fixed this "bug" because it affects
> other load/store instructions under some conditions (i.e. this isn't
> unique to the cache instructions).
OK so this is not it then, but what is it then? Are you 100% that
the bug(whatever this may be) is present for mpc860, rev D4 or later?
How can I make it bite me on kernel space memory?
I can't find that info in the archives, if it's there please give me a hint.
I have enabled all kernel functions that uses dcbz for 8xx as well. I even split copy_tofrom_user
into copy_from_myuser resp. copy_to_myuser and enabled dcbz in copy_from_myuser
and still everything is working just fine.
Jocke
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-03 23:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 17:50 Improved copy_page() function, about 30% speed up for mpc860! Joakim Tjernlund
2003-03-03 21:18 ` Dan Malek
2003-03-03 23:16 ` Joakim Tjernlund [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-02-27 13:08 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
2003-03-04 0:19 ` Paul Mackerras
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='006a01c2e1da$e108ddd0$020120b0@jockeXP' \
--to=joakim.tjernlund@lumentis.se \
--cc=dan@embeddededge.com \
--cc=drow@false.org \
--cc=linuxppc-dev@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).