From: Liang Ma <liangma@liangbit.com>
To: 王颢 <howard_wang@realsil.com.cn>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: About DPDK l3fwd
Date: Tue, 3 Dec 2024 16:13:13 +0000 [thread overview]
Message-ID: <Z08uGUEksLFyfsnb@CTQ0WR29WC> (raw)
In-Reply-To: <5ac7c2183b4b4cbebff6e36efee37b3e@realsil.com.cn>
On Fri, Nov 22, 2024 at 09:45:58AM +0000, 王颢 wrote:
> Dear all,
>
> I have noticed that the performance reports on the official DPDK website predominantly use l3fwd, while we typically utilize pktgen. Out of curiosity, I attempted to replicate the experiments from the performance reports. However, I encountered some issues, as shown in the attached image.
>
> I ran pktgen on PC1 and l3fwd on PC2. After establishing the connection, I entered the command str on pktgen. It appears that pktgen is able to send and receive packets normally, but there is no output from l3fwd. Based on my understanding, l3fwd should produce some output, correct?
>
> Could you please share how you usually conduct these tests for your performance reports?
>
> Thank you for your assistance.
>
> Best regards,
> Howard Wang
>
> [cid:image001.png@01DB3D05.9B91B530]
>
> [cid:image002.png@01DB3D05.9B91B530]
Hi Howard,
You can check out the performance test report. In most cases, the report will include all setup details (including the command line).
Regards
Liang
prev parent reply other threads:[~2024-12-03 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 9:45 王颢
2024-12-03 16:13 ` Liang Ma [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=Z08uGUEksLFyfsnb@CTQ0WR29WC \
--to=liangma@liangbit.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=howard_wang@realsil.com.cn \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).