linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: acurtis@onz.com
Cc: Ppc Developers <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 8260 Network Performance update
Date: Thu, 06 Jun 2002 13:16:51 -0400	[thread overview]
Message-ID: <3CFF9903.9000203@embeddededge.com> (raw)
In-Reply-To: NCBBIINEHIPFGJPLBEIFCEECDIAA.acurtis@onz.com


Allen Curtis wrote:

> 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.

That isn't the number of buffers, it's the number of buffer pages, so don't
go overboard allocating these.  The 8260 is going to fill buffers and shove
packets up the IP stack as fast as they appear on the wire.  Adding buffers
at the driver level will just cover up processing latencies by the application.

> 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?

The only thing that will happen is the IP stack will start tossing packets
if there is a memory shortfall.

> ..... I do not have this problem on a x86 RedHat
> system...

Are you doing _exactly_ the same thing?  It still looks like you have a
hardware configuration problem on the link, because I know other boards
will operate with the same software at the limit of the 10 or 100 Mbit
throughput.


	-- Dan


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-06 17:16 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
2002-06-06 17:16     ` Dan Malek [this message]
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=3CFF9903.9000203@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=acurtis@onz.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).