From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: bai bakari <912873551@qq.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] The performance of test-pipeline and l2fwd?
Date: Thu, 13 Dec 2018 18:15:03 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E8146F6@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <tencent_20A51F1D094FBE360DEA0810102106CE0B07@qq.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of bai bakari
> Sent: Thursday, December 13, 2018 9:50 AM
> To: dev <dev@dpdk.org>
> Subject: [dpdk-dev] The performance of test-pipeline and l2fwd?
>
> Hi,
>
> I test the performance of test-pipeline and l2fwd, and get the conclusion is:
> l2fwd is three times better than test-pipeline, that confused me.
> In principle it should be test-pipeline is better than l2fwd?
>
>
> Anyone can tell me the reason, thank you in advance.
How did you test it? Command line and setup description should help understanding what you're trying to do.
Thanks,
Cristian
prev parent reply other threads:[~2018-12-13 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 9:49 bai bakari
2018-12-13 18:15 ` Dumitrescu, Cristian [this message]
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=3EB4FA525960D640B5BDFFD6A3D891268E8146F6@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=912873551@qq.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).