netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Donald Becker <becker@scyld.com>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: NAPI-ized tulip patch against 2.4.20-rc1
Date: Thu, 07 Nov 2002 15:29:46 -0800	[thread overview]
Message-ID: <3DCAF76A.9080409@candelatech.com> (raw)
In-Reply-To: 3DCA1152.7040002@candelatech.com

Ben Greear wrote:
> 
> Here's an update of the tulip-NAPI and skb-recycle patches.  I made some
> changes to get it to compile and work when the RECYCLE define in skbuff.h
> was not enabled.
> 
> I also got some test runs in.  Nothing really conclusive.
> 
> Test setup:  Phobos 4-port NIC in each P-IV 1.8Ghz machine 32/33 PCI bus.
> Kernel 2.4.20-rc1 + my patches.  NICs connected to each other over CX 
> cables.
> Sending 4k 1514 byte packets per second, send + receive. (48Mbps or so)
> RX ring size is 1024 for all of these tests.  No significant errors 
> reported
> by the driver.  I don't know where these dropped packets go..no counter
> seems to be catching them.

I changed to use smaller packets 757 bytes long, and to send/receive twice
as many (8kpps).  Still running at 50Mbps or so.

rx-ring is 256, still using skb-recycling with 300 skb hotlist.

Out of 57 million sent, dropped about 24k packets.  I also see about
3k of Rx-Drops on each interface.  No other significant errors reported
by the driver....

Any ideas for what to try next?  What about upping the skb-hotlist to
1024 or so?  Maybe also pre-load it with buffers to make it less likely we'll
run low?  (Rx-Drops means it could not allocate a buffer, right?)

Enjoy,
Ben

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

  parent reply	other threads:[~2002-11-07 23:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06  6:36 NAPI-ized tulip patch against 2.4.20-rc1 Ben Greear
2002-11-06  6:42 ` Ben Greear
2002-11-06 17:34 ` Robert Olsson
2002-11-06 17:49   ` Ben Greear
2002-11-06 18:31     ` Donald Becker
2002-11-06 18:44       ` Ben Greear
2002-11-06 20:47         ` Donald Becker
2002-11-07  7:08           ` Ben Greear
2002-11-07 13:24             ` jamal
2002-11-07 18:16               ` greear
2002-11-07 21:26                 ` Robert Olsson
2002-11-07 21:25                   ` Ben Greear
2002-11-07 23:29             ` Ben Greear [this message]
2002-11-08 11:30               ` jamal
2002-11-08 17:40                 ` Ben Greear
2002-11-07 12:57           ` jamal
2002-11-06 19:47     ` Robert Olsson
2002-11-06 21:30       ` Ben Greear
2002-11-07 12:48   ` jamal

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=3DCAF76A.9080409@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=becker@scyld.com \
    --cc=netdev@oss.sgi.com \
    /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).