From: hao wang <imhowardwang@gmail.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: users@dpdk.org
Subject: Re: cannot trx when use testpmd
Date: Mon, 15 Apr 2024 10:22:07 +0800 [thread overview]
Message-ID: <CAPxtyi_rfgkZ71S1da5fvO__hDDLRxNtz=xuFcUj5cL1nonMmA@mail.gmail.com> (raw)
In-Reply-To: <9ec11232-4fe9-485c-98e1-d01d333a9c2e@amd.com>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
Dear ferruh,
I am currently engaged in working on the Realtek R8125 and R8126 projects.
Should I manage to overcome the current issue, I intend to contribute my
PMD upstream for inclusion in the v24.07 release. In the meantime, I will
continue to delve deeper into the debugging process in order to gather more
specific and pertinent details.
Thank you very much.
Hao
Ferruh Yigit <ferruh.yigit@amd.com> 于2024年4月12日周五 19:01写道:
> On 4/12/2024 8:51 AM, hao wang wrote:
> > 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?
> >
> >
>
> Hi Hao,
>
> I am not aware of any known issues in testpmd that may cause this
> specific problem.
> And without more details it is not possible to know what the issue is.
>
> What is the PMD you are working on? Are you planning to upstream it for
> v24.07 release?
>
>
> Also I assume you are checking 'atlantic' driver code only as sample, is
> this correct?
>
>
> Thanks,
> ferruh
>
>
[-- Attachment #2: Type: text/html, Size: 1915 bytes --]
next prev parent reply other threads:[~2024-04-15 2:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 7:51 hao wang
2024-04-12 11:01 ` Ferruh Yigit
2024-04-15 2:22 ` hao wang [this message]
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='CAPxtyi_rfgkZ71S1da5fvO__hDDLRxNtz=xuFcUj5cL1nonMmA@mail.gmail.com' \
--to=imhowardwang@gmail.com \
--cc=ferruh.yigit@amd.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).