linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: joakim.tjernlund@lumentis.se
Cc: Tom Rini <trini@kernel.crashing.org>,
	Daniel Jacobowitz <drow@false.org>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: Improved copy_page() function, about 30% speed up for mpc860!
Date: Tue, 04 Mar 2003 17:41:16 -0500	[thread overview]
Message-ID: <3E652B8C.8080602@embeddededge.com> (raw)
In-Reply-To: IGEFJKJNHJDCBKALBJLLEEMPFKAA.joakim.tjernlund@lumentis.se


Joakim Tjernlund wrote:

> I can't find any further info about this bug/workaround. There is nothing in
> linux that indicates that the workaround is dependant on any revision.

That's because we couldn't determine which ones in particular may be
broken.  Remember there are several different sources of cores, the 823/850
core is different from the 860 core.  We don't distinguish among these
in the kernel.

> Further, dcbi and dcbz are pretty similar in behavior w.r.t TLB error so
> I suspect that if this works for dcbi it also works for dcbz, only
> on kernel addresses though.

Maybe.

> Maybe user space also can be fixed with instruction decoding

No, user space has always been "fixed" by providing a unique version
of C libraries for the 8xx.  This has to be done for more reasons
than just the cache instructions.  It also includes supporting a
different sized cache line for dynamic relocation and often the
performance advantage of using soft-float instead of kernel emulated
floating point.  It's also perfectly suited for the IBM 403, BTW :-)

> as Daniel said even if it's ugly. Then you would not have to worry about
> apps/libs using dcbz, at least it would work but perhaps the performance sucks

I'm trying to discourage you guys from wasting time here.  These are
all known problems that have been solved.  If we want to use this processor
we have to accept some limitations and get on with using it. :-)  People
have been successfully deploying products for years using Linux and 8xx.
Leave the cache instructions alone.  :-)

This discussion has been moved to a very low priority in my mailbox.
Don't expect timely or any further replies, and please don't be sending me
any dcbz kernel patches! :-)

Thanks.


	-- Dan


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-03-04 22:41 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
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 [this message]
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=3E652B8C.8080602@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=drow@false.org \
    --cc=joakim.tjernlund@lumentis.se \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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).