All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: tg3 (netgear 302t) performance numbers
Date: Wed, 09 Oct 2002 18:10:27 -0700	[thread overview]
Message-ID: <3DA4D383.1010006@candelatech.com> (raw)

After placing my Netgear 302t NICs into my SS50 P-IV (1.8Ghz)
machine, they seem to work fine.  (They had various problems in
my AMD machines, but that could all just be coincidence and other,
non-related, problems)

My test-bed has two of these NICs connected to each other via
a cross-over cable.  Both NICs are in the same machine...

Here are some performance numbers I see:

tcp/ip send + receive in user-space:
   112Mbps on each port (does not count any packet over-head,
     and my generator/receiver is not the fastest thing around)

pktgen (kernel pkt generator module):
   60-byte packets, sending 1kpps in one direction, and maximum possible
   in the other.  Was able to generate 122,000 packets-per-second.
   (A tulip 10/100 NIC can do 140kpps in this configuration)
   Average Latency: 22 micro-seconds.
   0 dropped packets over 10+ minute run.

   1514-byte packets, sending 1kpps in one direction, max possible in
   the other.  25.8kpps (310Mbps) in the fast direction.
   Average Latency:  17 miliseconds (127 micro-seconds for the 1kpps direction)
   2000 dropped pkts, 5.8 million sent during this test.


So, not too bad, probably the 32/33 PCI bus is most of the bottle-neck.
The good part is, no errors or other strangnesses were seen with the driver.

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



             reply	other threads:[~2002-10-10  1:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10  1:10 Ben Greear [this message]
2002-10-10  1:29 ` tg3 (netgear 302t) performance numbers Ben Greear

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=3DA4D383.1010006@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.