From: Stephen Hemminger <shemminger@vyatta.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Jesper Dangaard Brouer <hawk@diku.dk>,
jon_zhou@agilent.com, netdev@vger.kernel.org
Subject: Re: the maximal speed of pktgen with 1Gbps NIC
Date: Wed, 22 Jul 2009 10:25:20 -0700 [thread overview]
Message-ID: <20090722102520.27a024ed@nehalam> (raw)
In-Reply-To: <1248275552.4058.0.camel@localhost>
On Wed, 22 Jul 2009 17:12:32 +0200
Ben Hutchings <bhutchings@solarflare.com> wrote:
> On Wed, 2009-07-22 at 14:56 +0200, Jesper Dangaard Brouer wrote:
> > On Wed, 22 Jul 2009, jon_zhou@agilent.com wrote:
> >
> > > anyone knows the maximal speed of pktgen with 1Gbps NIC?
> >
> > You are limited by the number of packets per second (pps) your machine can
> > generate. This limitation is given by the CPU speed and the NIC used.
> >
> > The maximum pps I have seen with pktgen at 1Gbit/s is 1200 kpps.
> >
> > 1Gbit/s wire speed pps with 64 bytes packets is approx 1953 kpps.
> > (1000*10^6/(64*8) = 1953125)
> [...]
>
> You need to take the inter-packet gap into consideration too.
>
> Ben.
Speed Packets/sec TCP MByte/sec
10 M 14880.95 1,170,351
100 M 148809.52 11,703,511
1 G 1488095.24 123,755,256
10 G 14880952.38 1,237,552,556
40 G 59523809.52 4,950,210,224
100 G 148809523.81 12,375,525,559
* TCP assumes timestamp option and jumbo frames if possible.
http://www.erg.abdn.ac.uk/users/gorry/course/lan-pages/enet-calc.html
--
prev parent reply other threads:[~2009-07-22 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 7:35 pktgen crash with 2.6.30 Or Gerlitz
2009-07-22 8:57 ` the maximal speed of pktgen with 1Gbps NIC jon_zhou
2009-07-22 12:56 ` Jesper Dangaard Brouer
2009-07-22 15:12 ` Ben Hutchings
2009-07-22 17:12 ` Bob Gilligan
2009-07-22 17:25 ` Stephen Hemminger [this message]
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=20090722102520.27a024ed@nehalam \
--to=shemminger@vyatta.com \
--cc=bhutchings@solarflare.com \
--cc=hawk@diku.dk \
--cc=jon_zhou@agilent.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 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.