From: Ben Greear <greearb@candelatech.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: netdev@oss.sgi.com
Subject: Re: Poor gige performance with 2.4.20-pre*
Date: Sun, 29 Sep 2002 12:32:38 -0700 [thread overview]
Message-ID: <3D975556.5070706@candelatech.com> (raw)
In-Reply-To: 200209291922.g8TJMA312403@vindaloo.ras.ucalgary.ca
Richard Gooch wrote:
> Ben Greear writes:
>
>>Richard Gooch wrote:
>>
>>> Hi, all. For a while now I've noticed poor performance with gige
>>>cards under 2.4.19 and 2.4.20-pre*. At first I thought it was because
>>>of the cheap-ass Addtron cards I bought (these use the ns83820 chip).
>>>But now that the Intel E1000 cards are pretty cheap too, I've grabbed
>>>a couple (part number: PWLA8390MT) and see the same problem. In fact,
>>>the E1000 cards are no better than the Addtron cards. I'm using the
>>>D-Link DGS-1008T 8-port gige switch. MTU=1500 bytes.
>>
>>Try setting the TxDescriptors=4096 RxDescriptors=1024 when loading the
>>e1000 module, that helps tremendously when using smaller packets.
>
>
> Didn't help at all. Just to summarise, I've got:
> options e1000 TxDescriptors=4096 RxDescriptors=1024
> net.ipv4.tcp_rmem = 262144 262144 262144
> net.ipv4.tcp_wmem = 262144 262144 262144
> MTU=1500
>
> I'm doing read(2)/write(2) to/from a user-space buffer over a TCP
> socket with 256 KiB buffer size.
>
> Is the E1000 supposed to have hardware interrupt mitigation (thus
> avoiding the need for NAPI)?
NAPI did not greatly improve the performance I saw with larger packets,
but it did help with smaller (say, 60 byte) packets.
One other thing I saw with TCP connections: They started off slow, but after
a few seconds they were reacing their peak throughput. How long are you running
your test?
Ben
>
> Regards,
>
> Richard....
> Permanent: rgooch@atnf.csiro.au
> Current: rgooch@ras.ucalgary.ca
>
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2002-09-29 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 22:57 Poor gige performance with 2.4.20-pre* Richard Gooch
2002-09-29 2:12 ` Xiaoliang (David) Wei
2002-09-29 6:34 ` Richard Gooch
2002-09-30 0:45 ` Benjamin LaHaise
2002-09-30 0:53 ` Richard Gooch
2002-09-29 2:32 ` Ben Greear
2002-09-29 19:22 ` Richard Gooch
2002-09-29 19:32 ` Ben Greear [this message]
2002-09-29 20:54 ` Richard Gooch
2002-09-30 21:21 ` Jon Fraser
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=3D975556.5070706@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
--cc=rgooch@ras.ucalgary.ca \
/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).