From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 03044A0548; Tue, 11 Oct 2022 19:54:04 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9BE4040687; Tue, 11 Oct 2022 19:54:04 +0200 (CEST) Received: from mail-pl1-f170.google.com (mail-pl1-f170.google.com [209.85.214.170]) by mails.dpdk.org (Postfix) with ESMTP id AD57240146 for ; Tue, 11 Oct 2022 19:54:03 +0200 (CEST) Received: by mail-pl1-f170.google.com with SMTP id b2so13902362plc.7 for ; Tue, 11 Oct 2022 10:54:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=4nTQNnxFNvyU0nHGHwUcDKG5ntgcX4maPpemqMXYtLU=; b=X023+ZWO4uG/efuRr61q+ydfZ8y324yQ3PySrRYD11jkm+QmaNPP2hbUga78t536RL 8RFeRLOqmz2+e1UFJGWQY9YzYyNhxIhO21xSH0pTzkQwfGHy40HxHY3GA0+xjunjMvV2 FZTSrwSAWDd+1iOVsLDWg8nIXo9+XZstTW1bjbGFHNNecs/RkYY6XDJc2+I9dfZVXsbs pw45cmIWSm9VJlOWO8Fb1cCNo8EBHWvuVYo7GArZ4MxnmhCVBOHnyj5yK2Fqsebu0POW 2TAS8HyXKNDI2inBa85eX4c63gOZCVoTudOmmqDTp3ewOTchY7O0FTfYP1dburuLX8ky EHtA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=4nTQNnxFNvyU0nHGHwUcDKG5ntgcX4maPpemqMXYtLU=; b=Q1zzHa62ZjO4nZhUnJLg/bLz712uVKvagmCgg4W/vOEJw8byuHk9Tj2kF1/OKQPjLO xP0I8dCf6MybZQh6rpgZN5o3bk8xFT7/mcgua+K330E+USZFrs7h7dix7y6/JPuGzd5Z Qp7A2saPVfRwqe3GdJhbayfSfBstcwp3cV+eW/GKiJ6xT831K1GT//Egc+lqTmf1QLSs bqmePA0fSLVzjx24tJEbHWNREZvx8TAmb200MaLbrxPiGR1tT1lIyfPdL9QQhDT8PMVo eN1P7lm5WuS4GjNtDnk8twJoewyxAKLBkUOXAd06JIQNx/21c5MW6mSpvIRhM6Zq901q 0hpA== X-Gm-Message-State: ACrzQf1/CONLvqx7Krep0eWvu34ZyYCj0AyrOVZ5kqB+0Znio4QDTbRv gFPi0ohNluWZE6r6CCewxXBW2w== X-Google-Smtp-Source: AMsMyM7FRSYWtEHqx06x6vgy7+vxJtA7eCIM+H0jgzAiFut0t1j1IrFB4XWBTTdso56Kl8MfXnTcrA== X-Received: by 2002:a17:90b:4a85:b0:20c:316d:e595 with SMTP id lp5-20020a17090b4a8500b0020c316de595mr346923pjb.186.1665510842627; Tue, 11 Oct 2022 10:54:02 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id f12-20020a63f10c000000b00440416463fesm6213643pgi.27.2022.10.11.10.54.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Oct 2022 10:54:02 -0700 (PDT) Date: Tue, 11 Oct 2022 10:54:00 -0700 From: Stephen Hemminger To: Ferruh Yigit Cc: dev@dpdk.org Subject: Re: [RFC] net: add experimental UDP encapsulation PMD Message-ID: <20221011105400.518aa1c2@hermes.local> In-Reply-To: References: <20221011001016.173447-1-stephen@networkplumber.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Tue, 11 Oct 2022 17:18:26 +0100 Ferruh Yigit 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 > > --- > > 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.