From: =?gb18030?B?YmFpIGJha2FyaQ==?= <912873551@qq.com>
To: =?gb18030?B?ZGV2?= <dev@dpdk.org>
Subject: [dpdk-dev] =?gb18030?q?About_the_comparation_of_=22test-pipeline?= =?gb18030?b?IiBhbmQgImwyZndkIqO/?=
Date: Tue, 11 Dec 2018 17:17:49 +0800 [thread overview]
Message-ID: <tencent_721D1B4FA6B603EA0B9059A1394E3E252907@qq.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 647 bytes --]
Hi,
I tested the performance of "test-pipeline"(--none) and "l2fwd", but the result confused me.
"l2fwd" was three times better than "test-pipeline" in pps.
I set them to the same parameters like this:
"l2fwd":
MAX_PKT_BURST=64
nb_rxd = 1024
nb_txd = 1024
"test-pipeline"
burst_size_rx_read = 64
burst_size_rx_write = 64
burst_size_worker_read = 64
burst_size_worker_write = 64
burst_size_tx_read = 64
burst_size_tx_write = 64
port_rx_ring_size = 1024
port_tx_ring_size = 1024
ring_rx_size = 1024
ring_tx_size = 1024
Can anyone know this reason and tell me? Thank you in advance.
Best wishes!
reply other threads:[~2018-12-11 9:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=tencent_721D1B4FA6B603EA0B9059A1394E3E252907@qq.com \
--to=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).