netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Fink <billfink@mindspring.com>
To: Ben Greear <greearb@candelatech.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: How fast can your 10G go?
Date: Wed, 20 May 2009 02:41:00 -0400	[thread overview]
Message-ID: <20090520024100.ceba4aca.billfink@mindspring.com> (raw)
In-Reply-To: <4A12D8D4.2070303@candelatech.com>

On Tue, 19 May 2009, Ben Greear wrote:

> I've been running some tests on a new Nehalem based system
> with a 2 port pci-e x8 10G NIC (ixgbe driver).
> 
> When using pktgen, max I can get is about 5.6Gbps tx + rx on both ports.  This is
> about 22Gbps across the backplane, so I don't mean to complain :)
> 
> However, I'm curious if anyone has gotten any better performance on
> some other system?  In particular, it seems that my system is bound by
> the bus and/or the NIC.  Would I need to find something like a x16 slot
> to have a chance at 10Gbps bi-directional on 2 ports?

We have achieved bidirectional 20-Gbps line rate traffic between a pair
of Nehalem i7 quad-core servers, each with a dual-port 10-GigE Myricom
PCI-E 2.0 x8 SFP+ NIC.  Here's a unidirectional 10-second nuttcp TCP
test (using 9000 byte jumbo frames):

[root@i7raid-1 ~]# ./nuttcp-6.2.6 -N2 -w10m /192.168.101.2/192.168.102.2
23627.0625 MB /  10.01 sec = 19792.4891 Mbps 53 %TX 57 %RX 0.11 msRTT

Your results sound about right for a PCI-E 1.0 x8 slot, which has
16 Gbps full-duplex usable bandwidth, and then subtracting about 25%
PCI-E overhead leaves about 12 Gbps full-duplex or 24 Gbps total
available bandwidth for TCP|UDP data transfers.

						-Bill

  reply	other threads:[~2009-05-20  6:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 16:05 How fast can your 10G go? Ben Greear
2009-05-20  6:41 ` Bill Fink [this message]
2009-05-21  8:35 ` Jesper Dangaard Brouer

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=20090520024100.ceba4aca.billfink@mindspring.com \
    --to=billfink@mindspring.com \
    --cc=greearb@candelatech.com \
    --cc=netdev@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 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).