From: "Allen Curtis" <acurtis@onz.com>
To: "Dan Malek" <dan@embeddededge.com>
Cc: "Ppc Developers" <linuxppc-dev@lists.linuxppc.org>
Subject: RE: 8260 Network Performance update
Date: Thu, 6 Jun 2002 05:41:39 -0700 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFCEECDIAA.acurtis@onz.com> (raw)
In-Reply-To: <3CFEF5FC.6050301@embeddededge.com>
> link parameters. You could try increasing the number of receive buffers
> in the Ethernet driver, and I guess we should modify the driver to DMA
> directly into skbufs. I would be surprised if either of these last two
> would increase the performance, but I've been surprised by a few
> things lately :-).
The table below is performance vs. number of driver buffers. (16 - 64)
10T Hub | 100BT switch
-------------------------------------|
16 RTB | 440KBps | 190KBps |
--------------------------------------
32 RTB | 450KBps | 230KBps |
--------------------------------------
64 RTB | 450KBps | 240KBps |
--------------------------------------
There is a slight improvement when you increase the number of buffers from
16 (default) to 32. There does not appear to be any benefit beyond that.
I am guessing that the problem is not in the driver unless the driver is
suppose to enforce some soft of fair usage algorithm. Is there a network
usage scheduler of some kind? I do not have this problem on a x86 RedHat
system...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-06 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 5:00 8260 Network Performance update Allen Curtis
2002-06-06 5:41 ` Dan Malek
2002-06-06 12:41 ` Allen Curtis [this message]
2002-06-06 17:16 ` Dan Malek
2002-06-06 12:31 ` Kenneth Johansson
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 4:55 Allen Curtis
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=NCBBIINEHIPFGJPLBEIFCEECDIAA.acurtis@onz.com \
--to=acurtis@onz.com \
--cc=dan@embeddededge.com \
--cc=linuxppc-dev@lists.linuxppc.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).