linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Jacky Lam <jackylam@astri.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Small UDP packet performance
Date: Mon, 19 Jan 2004 17:02:27 -0800	[thread overview]
Message-ID: <20040120010227.GA32018@gate.ebshome.net> (raw)
In-Reply-To: <015501c3deef$27263030$9104050a@JACKYLAM>


On Tue, Jan 20, 2004 at 08:48:38AM +0800, Jacky Lam wrote:
>
>     Thanks. My case is that I am using NetPerf to test the UDP performance.
> I am using a x86 with GigaEthernet card and sending packet to my 405EP in
> full speed. I find that the box nearly dead in first min and lost all
> packets. I know that it is unavoidable. But I want to know anyway to improve
> as much as possible.
>
>     What is NAPI? How can I make use of it?

Please, use google as I suggested and you find good discussion of the
problem you are experiencing.

Right now, there is no publicly available NAPI-enabled  driver for
4xx, although I have something done in that direction, but unfortunately
I put this task on hold because of more urgent problems :( (maybe I'll
return to it this or next month)

> Is there any buffer size in UDP stack that I can adjust?

No, it has nothing to do with UDP socket buffer size.

Eugene


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

  reply	other threads:[~2004-01-20  1:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19  3:44 Small UDP packet performance Jacky Lam
2004-01-19  5:28 ` Eugene Surovegin
2004-01-19  5:47   ` Eugene Surovegin
2004-01-20  0:48   ` Jacky Lam
2004-01-20  1:02     ` Eugene Surovegin [this message]
2004-01-20 23:23       ` Andrew May
2004-01-21  1:16         ` Eugene Surovegin
2004-01-21  2:05           ` Andrew May
2004-01-21  3:38             ` Eugene Surovegin
2004-01-22  9:26             ` Jacky Lam

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=20040120010227.GA32018@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=jackylam@astri.org \
    --cc=linuxppc-embedded@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).