public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Christian Reis <kiko@async.com.br>
Cc: eepro100@scyld.com, nfs@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [NFS] General network slowness on SIS 530 with eepro100
Date: 14 Aug 2002 03:13:55 +0200	[thread overview]
Message-ID: <shs1y92p7ho.fsf@charged.uio.no> (raw)
In-Reply-To: <20020813212923.L2219@blackjesus.async.com.br>

>>>>> " " == Christian Reis <kiko@async.com.br> writes:

     > Helle there,

     > I've been, for the past days, setting up a fairly big diskless
     > network based on Linux. I've chosen to use 2.4.19 as the kernel
     > because there were some hardware requirements, and for most of
     > the newer boxes, it runs fine. However, for three of the older
     > boxes, we have had some pretty odd performance and stability
     > issues. This message is about the latest one, which is an ASUS
     > P5S-B (has the infamous SIS 530 chipset) on an intel eepro100
     > card. Details:

Is all this NFS over UDP? If so, numbers should not really have
changed in 2.4.19 ( - yes my patchset changes things, but stock 2.4.19
should not be too different w.r.t 2.4.18)

Are you able to determine where in the 2.4.19-pre series the
performance dies?

Cheers,
  Trond

  reply	other threads:[~2002-08-14  1:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14  0:29 General network slowness on SIS 530 with eepro100 Christian Reis
2002-08-14  1:13 ` Trond Myklebust [this message]
2002-08-14  1:50   ` [NFS] " Christian Reis
2002-08-15 23:40   ` Christian Reis
2002-08-15 13:41 ` Denis Vlasenko
2002-08-15 19:21   ` Christian Reis
2002-08-16 13:21     ` Denis Vlasenko
2002-08-16 19:56       ` Christian Reis

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=shs1y92p7ho.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=eepro100@scyld.com \
    --cc=kiko@async.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.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