From: takada <takada@mbf.nifty.com>
To: lsorense@csclub.uwaterloo.ca
Cc: pcnet32@verizon.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: MediaGX/GeodeGX1 requires X86_OOSTORE.
Date: Sat, 17 Feb 2007 23:11:13 +0900 (JST) [thread overview]
Message-ID: <20070217.231113.193678444.takada@mbf.nifty.com> (raw)
In-Reply-To: <20070217000019.GH7582@csclub.uwaterloo.ca>
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
Subject: Re: MediaGX/GeodeGX1 requires X86_OOSTORE. (Was: Re: Strange connection slowdown on pcnet32)
Date: Fri, 16 Feb 2007 19:00:19 -0500
> 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.
is it mean what doesn't help with doesn't call set_cx86_reoder()?
this function disable to reorder at 0x4000:0000 to 0xffff:ffff.
does pcnet32 access at out of above range?
--- arch/i386/Kconfig.cpu~ 2007-02-05 03:44:54.000000000 +0900
+++ arch/i386/Kconfig.cpu 2007-02-17 21:25:52.000000000 +0900
@@ -322,7 +322,7 @@ config X86_USE_3DNOW
config X86_OOSTORE
bool
- depends on (MWINCHIP3D || MWINCHIP2 || MWINCHIPC6) && MTRR
+ depends on (MWINCHIP3D || MWINCHIP2 || MWINCHIPC6) && MTRR || MGEODEGX1
default y
config X86_TSC
next prev parent reply other threads:[~2007-02-17 14:12 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 ` MediaGX/GeodeGX1 requires X86_OOSTORE. (Was: Re: Strange connection slowdown on pcnet32) Lennart Sorensen
2007-02-17 0:00 ` Lennart Sorensen
2007-02-17 14:11 ` takada [this message]
2007-02-17 15:07 ` MediaGX/GeodeGX1 requires X86_OOSTORE 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=20070217.231113.193678444.takada@mbf.nifty.com \
--to=takada@mbf.nifty.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--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®