linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gerhard Jaeger <g.jaeger@sysgo.com>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [BUG] IBM440GX works too slow under nfsroot
Date: Mon, 25 Oct 2004 08:47:00 +0200	[thread overview]
Message-ID: <200410250847.00907.g.jaeger@sysgo.com> (raw)
In-Reply-To: <20041025011654.GA3290@gate.ebshome.net>

On Monday 25 October 2004 03:16, Eugene Surovegin wrote:
> On Fri, Oct 22, 2004 at 01:29:55AM -0700, Eugene Surovegin wrote:
> > FWIW, I haven't seen any problems when testing my new EMAC driver with
> > 100Mb hub, maybe it's only 10Mb related.
> >
> > Anyway, this is first time I'm hearing about half duplex problems,
> > Matt just mentioned them on IRC to me.
> >
> > I'll try to do some tests this weekend, although I have to admit half
> > duplex doesn't seem very important these days, nevertheless, if this
> > can be fixed, we better do this :).
>
> OK, I did some tests with 2.4.28-pre4, 2.6.9 & 2.6.9-emac (2.6.9 with
> my new EMAC driver). I used Ocotea rev.3 with 440GX rev.C (533MHz).
>
> I can confirm I see some problems in 10HDX mode - there is visible
> slow down during system boot up (NFS root). Just after logging into
> system, nfsstat shows around 350 retransmits.
>
> My 2.6.9-emac tree doesn't show this behavior, I see no visible
> slow-down and nfsstat shows 0 retransmits.
>
> I tried some quick hacks for 2.6.9 driver but was unable to find
> settings which could help (my new driver was almost re-written from
> scratch and I did a lot of things differently).

Hmmm, that's what we also found out, nothing really helped.

> For *adventurous*, this new EMAC driver is available as a patch against
> 2.6.9 BK tree at http://kernel.ebshome.net/. Please, note, it's still
> project in progress and it lacks support for all new 440GX features
> (GigE, TAH, jumbo frames, EMAC2/EMAC3). This is NAPI version with
> correct (I hope) error handling, chip access etc. On Ebony I was able
> to route around 144Kpps. I plan to implement support for _some_ 440GX
> new features soon (during next month, hopefully).

I will give it a try ASAP.

>
> If there is an interest, I can make a patch against current 2.4 BK
> tree, but this will take some time (I'm a little swamped right now).

of course there's some interest, at least by me ;) Would be great if you'll
find some time for that.

Thank you,
  Gerhard

  reply	other threads:[~2004-10-25  7:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21 23:57 [BUG] IBM440GX works too slow under nfsroot Hiroshi DOYU
2004-10-22  1:19 ` Eugene Surovegin
2004-10-22  1:26   ` Hiroshi DOYU
2004-10-22  1:33 ` Eugene Surovegin
2004-10-22  1:38   ` Hiroshi DOYU
2004-10-22  2:02     ` Eugene Surovegin
2004-10-22  6:26       ` Gerhard Jaeger
2004-10-22  8:29         ` Eugene Surovegin
2004-10-22  9:39           ` Gerhard Jaeger
2004-10-22 12:22           ` Mark Chambers
2004-10-22 12:27             ` Gerhard Jaeger
2004-10-25  1:16           ` Eugene Surovegin
2004-10-25  6:47             ` Gerhard Jaeger [this message]
2004-10-25  7:02               ` Eugene Surovegin
2004-11-08  2:55               ` Eugene Surovegin
2004-10-22 22:22     ` Matt Porter
  -- strict thread matches above, loose matches on Subject: below --
2004-10-22  5:57 Daren Hayward
2004-10-22  6:30 ` Gerhard Jaeger
2004-10-22  7:36 Neil Wilson

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=200410250847.00907.g.jaeger@sysgo.com \
    --to=g.jaeger@sysgo.com \
    --cc=ebs@ebshome.net \
    --cc=linuxppc-embedded@ozlabs.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).