From: hao wang <imhowardwang@gmail.com>
To: users@dpdk.org
Subject: cannot trx when use testpmd
Date: Fri, 12 Apr 2024 15:51:01 +0800 [thread overview]
Message-ID: <CAPxtyi8YdObkOH-RvpKjQQU9qUyXfUr2L_PRh=31Po4-wDty-A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
I have a pmd that I am upstreaming to DPDK and currently testing. When I
use testpmd to test my pmd, I found that my pmd could trx in DPDK 23.07,
but it cannot in DPDK 23.11. After comparing the atlantic pmd between DPDK
23.07 and 23.11, I see nearly no changes. I see the testpmd difference
between DPDK 23.07 and DPDK 23.11 and think these changes may not cause the
problem.
But when I use pktgen to test the pmd, it's ok.
Any suggestions?
Thank you very much!
[-- Attachment #2: Type: text/html, Size: 565 bytes --]
next reply other threads:[~2024-04-12 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 7:51 hao wang [this message]
2024-04-12 11:01 ` Ferruh Yigit
2024-04-15 2:22 ` hao wang
2024-04-15 7:11 ` David Marchand
2024-04-16 7:46 ` hao wang
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='CAPxtyi8YdObkOH-RvpKjQQU9qUyXfUr2L_PRh=31Po4-wDty-A@mail.gmail.com' \
--to=imhowardwang@gmail.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).