From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: dev@dpdk.org
Subject: Re: [RFC] net: add experimental UDP encapsulation PMD
Date: Tue, 11 Oct 2022 10:54:00 -0700 [thread overview]
Message-ID: <20221011105400.518aa1c2@hermes.local> (raw)
In-Reply-To: <adc88cd3-1b2f-5333-ee03-637696068d5f@amd.com>
On Tue, 11 Oct 2022 17:18:26 +0100
Ferruh Yigit <ferruh.yigit@amd.com> wrote:
> On 10/11/2022 1:10 AM, Stephen Hemminger wrote:
> > This is a new PMD which can be useful to test a DPDK application
> > from another test program. The PMD binds to a connected UDP socket
> > and expects to receive and send raw Ethernet packets over that
> > socket.
> >
>
> Why is the 'connected UDP socket' requirement? I guess this maps with
> 'SO_REUSEPORT' in the code.
>
> > This is especially useful for testing envirionments where you
> > can't/don't want to give the test driver program route permission.
> >
> > Signed-off-by: Stephen Hemminger<stephen@networkplumber.org>
> > ---
> > This is 1st draft port of some test infrastructure to get
> > feedback and comments from community.
> >
> > Later version will include an example and unit tests.
>
> I think pcap PMD can be used for similar testing purposed, but we can
> have UDP PMD too, it may open other possibilities as a method to
> communicate with other non-dpdk applications.
>
> Although this is draft I will put some comments in other thread for next
> version.
Our use case was unique. We are testing application running in QEMU on Windows
and the test driver is a Windows application. The Windows application interacts
with DPDK inside QEMU over UDP. For example, test driver builds a packet and
sends it to the DPDK appliance and expects a given result: rewrite, drop, etc.
next prev parent reply other threads:[~2022-10-11 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 0:10 Stephen Hemminger
2022-10-11 6:47 ` Morten Brørup
2022-10-11 14:06 ` Stephen Hemminger
2022-10-11 16:18 ` Ferruh Yigit
2022-10-11 17:54 ` Stephen Hemminger [this message]
2022-10-11 16:48 ` 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=20221011105400.518aa1c2@hermes.local \
--to=stephen@networkplumber.org \
--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).