linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: joakim.tjernlund@lumentis.se
Cc: 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 08:33:31 -0500	[thread overview]
Message-ID: <3E64AB2B.6030804@embeddededge.com> (raw)
In-Reply-To: IGEFJKJNHJDCBKALBJLLIEMEFKAA.joakim.tjernlund@lumentis.se


Joakim Tjernlund wrote:

> I and Daniel discussed it, mostly in private. It fails horribly for
> me too in user space(init hangs, don't know any details) and that's why
> I split copy_tofrom_user into 2 functions( see yesterdays mail) as a test. With that
> change my system is stable.

Well, I suspect it's luck more than stable. :-)

I suggest you debug the failure cases and determine what is really
wrong.  We know from past history that the cache instructions on 8xx
are troublesome and if we avoid them the system is truly stable.  The
execution of the cache instructions is identical whether you are using
them on kernel or user pages, the main difference is you are more likely
to hit TLB refill/update cases when using user space pages, exactly
one of the problem triggers.  If it's working on kernel pages and not
user pages, or some other combinations, you are just being lucky.  The
cache instructions will do the right thing if the mapping is present
in the TLB (and you don't get a write/update miss) and the page is
cached.  If you don't have the page cached or you get any TLB exception
the results are unpredictable and the result varies depending upon
silicon revision.

This is something that is difficult to debug and we can't dismiss this
with a solution of different copy functions.  The clear/copy functions
for the 8xx should be identical to all other PowerPC cores, and if they
don't work that way we need to determine why.  At least you have the
knowledge that these instructions are troublesome.  It took me many months
to discover this the first time, and perhaps they still misbehave.

Thanks.


	-- Dan


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

  reply	other threads:[~2003-03-04 13:33 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 [this message]
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=3E64AB2B.6030804@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=drow@false.org \
    --cc=joakim.tjernlund@lumentis.se \
    --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).