mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: pcnet32@verizon.net
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: MediaGX/GeodeGX1 requires X86_OOSTORE. (Was: Re: Strange connection slowdown on pcnet32)
Date: Fri, 16 Feb 2007 19:00:19 -0500	[thread overview]
Message-ID: <20070217000019.GH7582@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20070216224824.GG7585@csclub.uwaterloo.ca>

On Fri, Feb 16, 2007 at 05:48:24PM -0500, Lennart Sorensen wrote:
> Well so far it really looks like enabling OOSTORE on the Geode
> SC1200/GX1 really does make a difference.  A bit of searching seems to
> indicate the person that originally submitted the patch that enabled
> load/store reordering on the MediaGX/Geode though it might need OOSTORE,
> but was convinced by others it didn't.  Looks like it really does need
> it.  The failure that occoured before within a few seconds of starting a
> large transfer, no longer fails and all I did was enable
> CONFIG_X86_OOSTORE, and recompile pcnet32.ko and load the new module on
> the running system.  Moving back to the pcnet32.ko built without OOSTORE
> enabled hits the failure again within seconds, until ifconfig eth1
> down/up reinitialized it's descriptor ring, after which it survices
> another bit of transfer and then fails again.

Well forcing load/store serialize on the CPU doesn't help, disalbing
memory bypass doesn't help.  Enabling the X86_OOSTORE does help.  What a
stupid CPU design.

So far nothing has managed to fix the __memcpy_toio in the jsm driver
getting data out of order when sending on an exar pci uart chip.  Only
calling memcpy with one byte at a time seems to work there.  Works fine
on every other cpu of course.  What else am I going to discover is wrong
with this CPU.

--
Len Sorensen

  reply	other threads:[~2007-02-17  0:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <32943920.1119801171642884331.JavaMail.root@vms226.mailsrvcs.net>
     [not found] ` <20070216172110.GC7582@csclub.uwaterloo.ca>
     [not found]   ` <20070216202300.GD7585@csclub.uwaterloo.ca>
     [not found]     ` <20070216210157.GE7585@csclub.uwaterloo.ca>
     [not found]       ` <20070216222728.GF7585@csclub.uwaterloo.ca>
2007-02-16 22:48         ` Lennart Sorensen
2007-02-17  0:00           ` Lennart Sorensen [this message]
2007-02-17 14:11             ` MediaGX/GeodeGX1 requires X86_OOSTORE takada
2007-02-17 15:07               ` Lennart Sorensen
2007-02-19 14:55               ` Lennart Sorensen
2007-02-19 19:48                 ` Roland Dreier
2007-02-19 19:57                   ` Lennart Sorensen
2007-02-19 23:56                   ` takada
2007-02-20  0:02                     ` Lennart Sorensen
2007-02-20 11:34                       ` takada
2007-02-20 14:48                         ` Lennart Sorensen
2007-03-15  5:39                           ` takada
2007-03-15 17:31                             ` Lennart Sorensen
2007-03-17 13:08                               ` takada
2007-03-19 18:23                                 ` Lennart Sorensen

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=20070217000019.GH7582@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pcnet32@verizon.net \
    /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

all inboxes | Powered by JetHome®