From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Cake] are anyone playing with dpdk and vpp?
Date: Wed, 27 Apr 2016 21:38:08 +0200 [thread overview]
Message-ID: <20160427193808.GA31326@sesse.net> (raw)
In-Reply-To: <CAOaVG17QaDgfehKjeWdVtB3chj_4PWwmog4j3b3gmL_zH7R6rA@mail.gmail.com>
On Wed, Apr 27, 2016 at 12:32:14PM -0700, Stephen Hemminger wrote:
> DPDK gets impressive performance on large systems (like 14M packets/sec per
> core), but not convinced on smaller systems.
I guess also “14M packets/sec/core for doing what”. If you want to implement
the dumbest switch in the world, then sure. If you want NAT, what kind of
performance do you get? How flexible is it wrt. user configuration?
/* Steinar */
--
Homepage: https://www.sesse.net/
next prev parent reply other threads:[~2016-04-27 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 18:57 [Bloat] " Dave Taht
2016-04-27 19:28 ` Aaron Wood
2016-04-27 19:32 ` [Bloat] [Cake] " Stephen Hemminger
2016-04-27 19:37 ` Mikael Abrahamsson
2016-04-27 19:38 ` Steinar H. Gunderson [this message]
2016-04-27 19:45 ` Dave Taht
2016-04-27 19:50 ` Dave Taht
2016-04-27 22:40 ` Aaron Wood
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160427193808.GA31326@sesse.net \
--to=sgunderson@bigfoot.com \
--cc=bloat@lists.bufferbloat.net \
/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