From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: "Xu, Chenjie" <chenjie.xu@intel.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] How to specify packet size of testpmd
Date: Thu, 9 Jul 2020 09:50:43 +0000 [thread overview]
Message-ID: <BYAPR11MB3143512DBC09630D26B7FF7CD7640@BYAPR11MB3143.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CY4PR11MB1560C28DE1D50064C520FEA68A640@CY4PR11MB1560.namprd11.prod.outlook.com>
> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Xu, Chenjie
> Sent: Thursday, July 9, 2020 10:26 AM
> To: users@dpdk.org
> Subject: [dpdk-users] How to specify packet size of testpmd
>
> Hi all,
> Do you know how to specify the packet size when using testpmd to test the
> network performance?
Hi,
Usually, testpmd just forwards the packets it receives. Testpmd itself is not a
"proper" traffic generator, but it does have some capabilities to send some traffic
before starting its rx-tx behavior.
The command is "start tx_first" and this will by default use a small packet size.
https://doc.dpdk.org/guides/testpmd_app_ug/testpmd_funcs.html#start-tx-first
There are a number of more powerful DPDK based traffic generators available,
if you require more features. Examples are pktgen, trex, moongen.
Of course, it is also possible to modify a sample application like example/skeleton
to send a specific traffic type, as your particular benchmarking might require.
> Best Regards,
> Xu, Chenjie
Hope that helps, -Harry
next prev parent reply other threads:[~2020-07-09 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 9:25 Xu, Chenjie
2020-07-09 9:50 ` Van Haaren, Harry [this message]
2020-07-10 8:58 ` Xu, Chenjie
2020-07-10 9:10 ` Mishal Shah
2020-07-10 9:15 ` Xu, Chenjie
2020-07-09 21:17 ` Cliff Burdick
2020-07-10 9:06 ` Xu, Chenjie
2020-07-11 1:49 ` Johnson, Brian
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=BYAPR11MB3143512DBC09630D26B7FF7CD7640@BYAPR11MB3143.namprd11.prod.outlook.com \
--to=harry.van.haaren@intel.com \
--cc=chenjie.xu@intel.com \
--cc=users@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).