DPDK patches and discussions
 help / color / mirror / Atom feed
From: Royce Niu <royceniu@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Why IP_PIPELINE is faster than L2FWD
Date: Thu, 22 Dec 2016 00:18:12 +0800	[thread overview]
Message-ID: <CAOwUCNs=c_5Ndb1+8zjJuhmA+i109XS5VjT00XvX-LpHP3GrWQ@mail.gmail.com> (raw)

Hi all,

I tested default L2FWD and IP_PIPELINE (pass-through). The throughput of
IP_PIPELINE is higher immensely.

There are only two virtual NICs in KVM. The experiment is just moving
packet from vNIC0  to vNIC1. I think the function is so simple. Why L2FWD
is much slower?

How can I improve L2FWD, to make L2FWD faster?

Thanks!

-- 
Regards,

Royce

             reply	other threads:[~2016-12-21 16:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 16:18 Royce Niu [this message]
2016-12-22 11:15 ` Bruce Richardson
2016-12-22 12:48   ` Royce Niu
2016-12-22 13:25     ` Bruce Richardson
2016-12-22 13:36       ` Royce Niu
2016-12-23  1:34         ` Xu, Qian Q
2016-12-23  1:41           ` Royce Niu

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='CAOwUCNs=c_5Ndb1+8zjJuhmA+i109XS5VjT00XvX-LpHP3GrWQ@mail.gmail.com' \
    --to=royceniu@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).