From: Ferruh Yigit <ferruh.yigit@amd.com>
To: wushaohua@chinatelecom.cn, dev@dpdk.org
Cc: aman.deep.singh@intel.com, yuying.zhang@intel.com,
Keith Wiles <keith.wiles@intel.com>,
"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [PATCH] app/testpmd:add vxlan txonly
Date: Fri, 17 Feb 2023 20:43:03 +0000 [thread overview]
Message-ID: <eb9a8e27-4eaf-ac7a-7d28-8b916122f6f0@amd.com> (raw)
In-Reply-To: <20230103023027.1893801-1-wushaohua@chinatelecom.cn>
On 1/3/2023 2:30 AM, wushaohua@chinatelecom.cn wrote:
> From: Shaohua Wu <wushaohua@chinatelecom.cn>
>
> Add the vxlan packet sending module to actively send
> vxlan packets using a common network adapter.
> The default vni is 1000.
> example:
> ./dpdk-testpmd -l 32-47 -n 16 --file-prefix pg0 -- -i
> --rxq=16 --txq=16 --rxd=1024 --txd=1024
> --txpkts=64 --burst=64 --mbuf-size=4096
> --nb-cores=15 --underlay_tx_only
> --underlay-eth-peer=0,f0:00:00:00:00:66
> --eth-peer=0,08:c0:eb:3e:87:af
> --utx-ip=11.0.0.1,11.0.0.2
> --tx-ip=30.0.0.1,30.0.0.2
> --forward-mode=tuntxonly
> --txonly-multi-flow
>
> Signed-off-by: Shaohua Wu <wushaohua@chinatelecom.cn>
Hi Shaohua,
This is a good feature but I am not sure if this is in the scope of
testpmd application.
Testpmd has basic packet generation capabilities, and it is useful for
quick/dirty testing, but for more advanced packet generation perhaps
other tools like pktgen [1] can be used, what do you think?
What is the justification to have this feature in testpmd, and what is
your usecase?
[1]
https://git.dpdk.org/apps/pktgen-dpdk/
next prev parent reply other threads:[~2023-02-17 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 2:30 wushaohua
2023-02-17 20:43 ` Ferruh Yigit [this message]
2023-02-18 11:06 ` wushaohua
2023-02-18 23:47 ` Ferruh Yigit
2023-03-06 12:07 ` Ferruh Yigit
2023-03-23 11:51 ` Ferruh Yigit
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=eb9a8e27-4eaf-ac7a-7d28-8b916122f6f0@amd.com \
--to=ferruh.yigit@amd.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=techboard@dpdk.org \
--cc=wushaohua@chinatelecom.cn \
--cc=yuying.zhang@intel.com \
/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).