From: Andrew May <acmay@acmay.homeip.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Small UDP packet performance
Date: Tue, 20 Jan 2004 18:05:01 -0800 [thread overview]
Message-ID: <20040121020501.GA22956@acmay.homeip.net> (raw)
In-Reply-To: <20040121011650.GA3905@gate.ebshome.net>
On Tue, Jan 20, 2004 at 05:16:50PM -0800, Eugene Surovegin wrote:
> On Tue, Jan 20, 2004 at 03:23:42PM -0800, Andrew May wrote:
> > Here is what I have done for a NAPI version of the driver. I don't have time
> > either to do a patch or merge this up to the latest kernel. I have frozen down
> > at 2.4.21-pre4 somewhere and I won't be merging anytime soon. It is stable for
> > me.
>
> Looks OK, although I chose another way to disable RX IRQs :)
Do tell.
> Sad thing is because of bad MAL design NAPI will be limited to one
> EMAC per MAL (there is no way to disable IRQ generation on channel
> basis), it's not an issue for 405, but for 440 I haven't figured
> out how to overcome this limitation yet.
Yep it is a problem and even for the 405's with more than one ethernet.
> Andrew, I'm just curious, you probably did some measurements with
> your NAPI driver, care to share them :) ?
It may be hard to compare them. I am adding some data to each packet
and routing them to another PCI device. I think things max out around
18kpps one way. Going full-duplex things even out pretty good both
ways with the total pps being slightly higher. The most important
thing is that when the input rate goes higher the output stays at
the max instead of going down.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-21 2:05 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
2004-01-20 23:23 ` Andrew May
2004-01-21 1:16 ` Eugene Surovegin
2004-01-21 2:05 ` Andrew May [this message]
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=20040121020501.GA22956@acmay.homeip.net \
--to=acmay@acmay.homeip.net \
--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).