public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <nivedita@sequent.com>
To: jw2357@hotmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Abysmal RECV network performance
Date: Mon, 28 May 2001 23:45:28 -0700 (PDT)	[thread overview]
Message-ID: <200105290645.XAA29714@eng4.sequent.com> (raw)

> Can someone please help me troubleshoot this problem - 
> I am getting abysmal (see numbers below) network performance 
> on my system, but the poor performance seems limited to receiving 
> data. Transmission is OK. 

[ snip ]

> What kind of performance should I be seeing with a P-90 
> on a 100Mbps connection? I was expecting something in the 
> range of 40-70 Mbps - certainly not 1-2 Mbps. 
> 
> What can I do to track this problem down? Has anyone else 
> had problems like this? 

While we didnt use 2.2 kernels at all, we did similar tests
on 2.4.0 through 2.4.4 kernels, on UP and SMP. I've used
a similar machine (PII 333MHz) as well as faster (866MHz) 
machines, and got pretty nifty (> 90Mbs) throughput on 
netperf tests (tcp stream, no disk I/O) over a 100Mb full
duplex link.  (not sure if there are any P-90 issues).

Throughput does drop with small MTU, very small packet sizes,
small socket buffer sizes, but only at extremes, for the most
part throughput was well over 70Mbs. (this is true for single
connections, you dont mention how many connections you were
scaling to, if any).

However, we did run into serious performance problems with
the Netgear FA311/2 (tulip). Found that the link lost
connectivity because of card lockups and transmit timeout 
failures - and some of these were silent. However, I moved 
to the 3C905C (3c59x driver) which behaved like a champ, and 
we didnt see the problems any more, so have stuck to that card.  
This was back in the 2.4.0 time frame, and there have many 
patches since then to various drivers, so not sure if the
problem(s) have been resolved or not (likely to have been,
extensively reported). Both your cards might actually be
underperforming..

Are you seeing any errors reported in /var/log/messages?
Are you monitoring your connection via tcpdump, for example?
You might sometimes see long gaps in transmission...Are
there any abnormal numbers in /proc/net/ stats? I dont remember
seeing that high frame errors, although there were a few. 

HW checksumming for the kind of test you are doing (tcp, mostly
fast path) will not buy you any real performance gain, the
checksum is actually consumed by the user-kernel copy routine.

You can also run the tests on a profiling kernel and compare
results... 

Nivedita

---
Nivedita Singhvi                        (503) 578-4580
Linux Technology Center                 nivedita@us.ibm.com
IBM Beaverton, OR                       nivedita@sequent.com



             reply	other threads:[~2001-05-29  6:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29  6:45 Nivedita Singhvi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-01  4:57 Abysmal RECV network performance John William
2001-06-01  5:22 ` Ben Greear
2001-06-01  3:50 John William
2001-06-01  4:56 ` Ben Greear
2001-05-30  2:55 John William
2001-05-31 16:40 ` Nivedita Singhvi
2001-05-28  3:47 John William
2001-06-01  6:13 ` Stephen Degler

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=200105290645.XAA29714@eng4.sequent.com \
    --to=nivedita@sequent.com \
    --cc=jw2357@hotmail.com \
    --cc=linux-kernel@vger.kernel.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