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 57286A0545; Tue, 11 Oct 2022 16:06:46 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 20B0E42DE1; Tue, 11 Oct 2022 16:06:46 +0200 (CEST) Received: from mail-pl1-f177.google.com (mail-pl1-f177.google.com [209.85.214.177]) by mails.dpdk.org (Postfix) with ESMTP id 06C5242B7D for ; Tue, 11 Oct 2022 16:06:44 +0200 (CEST) Received: by mail-pl1-f177.google.com with SMTP id h10so13303656plb.2 for ; Tue, 11 Oct 2022 07:06:44 -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=XSRNDIKwBGpxSt8qwjO/vbe42T0BIEzIt/5fT9PIGuU=; b=wHEK90XQjGo2NN1na7NQIZE6JSp1jxYXOjInxlDrkpcCwYP8zbhHEII7B83TaAYsvq bh2tH/29v011zrM4WZBK4ZpC+tjA15O/4GTnluFqR1+/AWNYZ1xZISEiwhNwOq/Fhltg kk7jH4V5B8YmSP4RgoXxl6SxIFaXvg6OgJDzRZ4ZjxhFQ05QVRbRQn2QC9llMjpBmQIL iKQhVpCKZ0mHSSynZkMQKHK7ei5swfWVd0DmOO84Y20HoA0PYuO3Ayv/TjnLiMFStw+h XGfp3JzrmFAT86kWzdvE/YqWW8qlqpIPK1ri+szHBB+SApJoU2Nh6XXISF+o/e2eFlsS HhUw== 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=XSRNDIKwBGpxSt8qwjO/vbe42T0BIEzIt/5fT9PIGuU=; b=yBheij9/pHoF/qPHN3/RKPBm81sExijmkLU0wTaAHziwYjDJeo4clF/QUERtGhG0cJ aDDHUhfiEpUTCIMSUd3HtmpqxFIP6j5NjVBpu8YMpUdkUidTCdYibUJaCTNX7IOaxquV nvQBLAjxuZJm0FcaMnRyD0qmCLxIOPswmHiYaYa2N6RoIyXJaTdBBcFe/Zo5r47q4oTb uAaBX9w7CRs287QI3+qhOLC9W3TNNjcpXsw43b5AZTr1/4Tf+HpMPhdGDq3G+sVjJ0yi OgesWR3ojcCy6G8Q0DL8PzChpdg2YD/fauZYNagbCIRoknHwv8Ln/1MamxH269m1Teor MooA== X-Gm-Message-State: ACrzQf3N3ZMnvGxgsxZpK0848HxBNMz2A3X5Tuw3CACuV2dBV1Sjcqdh 4LFeXEKW+bYmUyjCbi1fEK+Jcgf013BWSA== X-Google-Smtp-Source: AMsMyM5ALieiuU0PoAhnZ6m5wHusRAUGUI7lJFqNXZ2QngE/9ZKFYWSDI6xWc3yErhbsSq0xsVTsKA== X-Received: by 2002:a17:90b:4b83:b0:20c:5ac8:1e30 with SMTP id lr3-20020a17090b4b8300b0020c5ac81e30mr21975537pjb.71.1665497204056; Tue, 11 Oct 2022 07:06:44 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id 23-20020a17090a0f1700b001efa9e83927sm10848712pjy.51.2022.10.11.07.06.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Oct 2022 07:06:43 -0700 (PDT) Date: Tue, 11 Oct 2022 07:06:41 -0700 From: Stephen Hemminger To: Morten =?UTF-8?B?QnLDuHJ1cA==?= Cc: Subject: Re: [RFC] net: add experimental UDP encapsulation PMD Message-ID: <20221011070641.33d7ba56@hermes.local> In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D873D0@smartserver.smartshare.dk> References: <20221011001016.173447-1-stephen@networkplumber.org> <98CBD80474FA8B44BF855DF32C47DC35D873D0@smartserver.smartshare.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 08:47:30 +0200 Morten Br=C3=B8rup wrote: > > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > > Sent: Tuesday, 11 October 2022 02.10 > >=20 > > 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. > >=20 > > This is especially useful for testing envirionments where you > > can't/don't want to give the test driver program route permission. > >=20 > > Signed-off-by: Stephen Hemminger > > --- =20 >=20 > Good idea. >=20 > Multiple queues are supported, but how does the remote application steer = traffic into specific queues (for PMD RX), or identify which queue the pack= et was supposed to egress on (for PMD TX)? For Tx it relies on the fact that a UDP socket is idempotent so multiple Tx= queues just share a single file descriptor. On Rx, there is no steering, it just has multiple threads reading on the sa= me socket. For testing this simulates multiple receivers being active. >=20 > You could use a range of UDP port numbers for that, so the second queue u= ses the UDP port number following the configured port number, etc.. >=20 > Or you could open for feature creep. Here are some thoughts. >=20 > Add a metadata header in front of each packet - this might also allow mor= e advanced use in the future, e.g. the remote application could set mbuf ha= sh fields. >=20 > Consider if this PMD somehow can be integrated with the TUN/TAP PMD or so= mething similar, and through that existing PMD support more advanced NIC fe= atures towards the DPDK application, such as VLAN stripping, GRO, etc.. The other alternative is making a VXLAN driver, which is on my TODO list.