From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: cake@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat] are anyone playing with dpdk and vpp?
Date: Wed, 27 Apr 2016 21:37:04 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1604272133510.16013@uplift.swm.pp.se> (raw)
In-Reply-To: <CAOaVG17QaDgfehKjeWdVtB3chj_4PWwmog4j3b3gmL_zH7R6rA@mail.gmail.com>
On Wed, 27 Apr 2016, Stephen Hemminger wrote:
> DPDK gets impressive performance on large systems (like 14M packets/sec per
> core), but not convinced on smaller systems.
> Performance depends on having good CPU cache. I get poor performance on
As soon as you can't find information in cache and have to go to RAM to
get it (and you need it to proceed), you've lost the impressive
performance.
VPP is all about pre-fetching (tell memory subsystem to go get information
into cache you probably will need in the not so distant future). It
actually reminds me of demo programming on C64/Amiga that I was involved
in in the 80ties. Lots of small optimisations needed to yield these
results.
So yes, cache is extremely important for VPP.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2016-04-27 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 18:57 [Cake] " Dave Taht
2016-04-27 19:28 ` [Cake] [Bloat] " Aaron Wood
2016-04-27 19:32 ` Stephen Hemminger
2016-04-27 19:37 ` Mikael Abrahamsson [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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1604272133510.16013@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=stephen@networkplumber.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