netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Gilligan <gilligan@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:12:17 -0700	[thread overview]
Message-ID: <4A674871.4090901@vyatta.com> (raw)
In-Reply-To: <1248275552.4058.0.camel@localhost>

Ben Hutchings 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.

Yes.  Usually when people talk about the "64-byte PPS rate" they are 
referring to the maximum rate of minimum size ethernet frames.  The 
64-bytes includes the src/dst addr fields, type field and CRC, but does 
not include the preamble (7 bytes), SOF (1 byte) or IPG (12 bytes). 
Adding these in  gives a minimum size frame of 84 bytes.  This works out 
to a max rate of ( 1,000,000,000 / (84 * 8) ) = 1,488,095 PPS.

Bob.


  reply	other threads:[~2009-07-22 17:12 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 [this message]
2009-07-22 17:25       ` Stephen Hemminger

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=4A674871.4090901@vyatta.com \
    --to=gilligan@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 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).