From: Vincent JARDIN <vincent.jardin@6wind.com>
To: Chris Pappas <chrispappas12@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] L3FWD LPM IP lookup performance question
Date: Mon, 30 Sep 2013 12:11:33 +0200 [thread overview]
Message-ID: <52494E55.4020507@6wind.com> (raw)
In-Reply-To: <CAE4G5iqr4w9COPRr--LzkaZtLaqZTuww1wjDkCFOkaL8VG8ApA@mail.gmail.com>
On 26/09/2013 23:16, Chris Pappas wrote:
> we are having some numbers regarding the performance of L3FWD and would
> like to confirm that they make sense.
> So, for L3FWD and 1500byte packets we get 120Gbps out of 12x10Gbps ports
> (so we get full throughput) and for 64byte packets we get 80Gbps.
12x10 with 80Gbps@64 bytes => 119Mpps
You did not describe your system: number of cores, sockets, PCIe slots, etc.
Whatever the HW environment you are using, you should run the same tests
but with testpmd in order to qualify the limits of the IOs for your
platform.
Best regards,
Vincent
next prev parent reply other threads:[~2013-09-30 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 13:53 Jun Han
2013-09-24 15:53 ` Vincent JARDIN
2013-09-26 21:16 ` Chris Pappas
2013-09-30 10:11 ` Vincent JARDIN [this message]
2013-10-01 8:57 Vladimir Medvedkin
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=52494E55.4020507@6wind.com \
--to=vincent.jardin@6wind.com \
--cc=chrispappas12@gmail.com \
--cc=dev@dpdk.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).