From: fengchengwen <fengchengwen@huawei.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Question about add ethdev loopback set API
Date: Wed, 14 Dec 2022 15:25:14 +0800 [thread overview]
Message-ID: <2d70ef33-5cc8-f56e-91c1-a44fd5450ba2@huawei.com> (raw)
In-Reply-To: <1109431c-2b18-cc02-5e36-5c1e2d298a82@amd.com>
On 2022/12/13 19:25, Ferruh Yigit wrote:
> On 12/13/2022 10:04 AM, fengchengwen wrote:
>> Hi Ferruh,
>>
>> During the test, we need to delineate where go wrong when encountered
>> e.g. CRC error. In this scenario, loopback is useful.
>>
>> I think we can add a loopback set API which could set inner or outer loop,
>> and user can use telemetry to set the loopback in the above scenario.
>>
>> I'd like to hear your opinion about add a loopback set API.
>>
>
> Hi Chengwen,
>
> Is the intention to test ethdev layer or driver?
>
> It is possible to use ring vdev to create a loopback and to test ethdev
> layer.
>
> For driver, it can be possible to create physical loopback connection,
> or even can implement loopback Rx/Tx burst functions in driver.
> Using another host to send/receive packets to DUT (device under test) is
> another approach.
>
>
> What kind of loopback implementation do you have in your mind?
Mainly MAC layer and lower physical layer:
-------- --------------- ------------ ---------- --------------------
| | | - rx | | - rx - | | - rx - | | |
| Host | - | MAC | - | SerDes | - | PHY | ==== | Packet Generator |
| | | - tx | | - tx - | | - tx - | | |
-------- --------------- ------------ ---------- --------------------
The support loopback in hns3 platform:
Inner loopback subtypes: which host send pkts and recv and then verify:
Serdes tx to rx
PHY tx to rx
Outer loopback subtypes: which Packet-Generator send pkts and recv and then verify:
MAC tx to rx
I think we could support the above loopback types, and maybe other PMD platform support
more loopback types.
>
>
> .
>
next prev parent reply other threads:[~2022-12-14 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 10:04 fengchengwen
2022-12-13 11:25 ` Ferruh Yigit
2022-12-14 7:25 ` fengchengwen [this message]
2022-12-14 10:38 ` Ferruh Yigit
2022-12-15 12:46 ` fengchengwen
2022-12-15 17:50 ` Ferruh Yigit
2022-12-16 1:07 ` fengchengwen
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=2d70ef33-5cc8-f56e-91c1-a44fd5450ba2@huawei.com \
--to=fengchengwen@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.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).