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 9F79F45D73 for ; Fri, 22 Nov 2024 20:51:44 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7A9C84028C; Fri, 22 Nov 2024 20:51:44 +0100 (CET) Received: from smtp1.cs.Stanford.EDU (smtp1.cs.stanford.edu [171.64.64.25]) by mails.dpdk.org (Postfix) with ESMTP id 006A040280 for ; Fri, 22 Nov 2024 20:51:42 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cs.stanford.edu; s=cs2308; h=Content-Type:To:Subject:Message-ID:Date:From: MIME-Version:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=+jPFqotVPsxwxb4W9isup6ZANLifzWV9lnZMMBpK6Cs=; t=1732305102; x=1733169102; b=e70k5kWyhO0MgYL67kkQXGhy33lU8E2o6FhrtfDL8GHE2mJlsLrxBOwl3+oH5DU+3pOif55z2G0 YLgi5Gbc9W4UEX4IuNtrgAmXSCHjGCIzh4F+NCQ34frBLPlqiLud415T9Rus6vbyb5sttFjIiWZqA bsPCaqRP2Euc7B8q9L6wjEPtSSo70r34+kUpM+Dhl9ytMZ2Br7wtHX0gQK6Sum3+Mz02TbSySI9m6 SAya8uLtYY2NfkMKYcNyb3k4a+v2lcHdQJXme9OU/obYTyQ41uD+tebbsEWUBbq5TB2EcIn3x5BeX s0owywAnVD/j/28Ds4nmF+O1etDMuCgCvdYA==; Received: from mail-pj1-f71.google.com ([209.85.216.71]:55336) by smtp1.cs.Stanford.EDU with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tEZgr-0004F2-1P for users@dpdk.org; Fri, 22 Nov 2024 11:51:41 -0800 Received: by mail-pj1-f71.google.com with SMTP id 98e67ed59e1d1-2ea46465ce4so2841374a91.2 for ; Fri, 22 Nov 2024 11:51:41 -0800 (PST) X-Gm-Message-State: AOJu0YzRfetrXq0K9wnm1qdgwvnJvUCJxj3/RKi+Q3PnlGKLRsaao+dE 7Q9DItCzU9SWDBy1CEK1IPt7Aio/jE+vWWduiko8oiGf1tqdCLeWR3nPpW0DFCu01sKN7kfFpn4 d+tyxwnkZARmL3ZZ12ZE62VUWn46VNQlQe7IMvEJouPO5LIEywT1mG0yYcDtYdUxyDTZf6Z/A1O nt09AHYaWSUW4xt8gdQ/3NFpricvDc6Q9XXq6RSBsfTnMSYYimKPDpZw== X-Gm-Gg: ASbGncuVrU7vBrxiaYzVREl0u8nH6tfP2PjIqQQK7PVyItwSP/UAM78EW3be4MiIKTj uIxW0zK/JH4pjU2S4fkLgsaxpd1MXDQ== X-Received: by 2002:a17:90b:3e8a:b0:2ea:3d4b:a0cc with SMTP id 98e67ed59e1d1-2eb0e02b13fmr5068282a91.7.1732305100156; Fri, 22 Nov 2024 11:51:40 -0800 (PST) X-Google-Smtp-Source: AGHT+IH/tdd3iLVNDI2pYd0Jqa7XrRnag+KSPR7yHEzyg19YepRZULZxs1OhyzJBMJB0qyvkFbCYQ6YM3V5t9JmV/1w= X-Received: by 2002:a17:90b:3e8a:b0:2ea:3d4b:a0cc with SMTP id 98e67ed59e1d1-2eb0e02b13fmr5068264a91.7.1732305099925; Fri, 22 Nov 2024 11:51:39 -0800 (PST) MIME-Version: 1.0 From: Thea Corinne Rossman Date: Fri, 22 Nov 2024 11:51:04 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: DPDK with Containernet To: users@dpdk.org Content-Type: multipart/alternative; boundary="0000000000001fcf43062785b6e0" X-proofpoint-id: ef3f9bb5-395f-4fcc-a797-849143d52903 X-Spam-Score: 0.8 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin on smtp1.cs.Stanford.EDU X-Scan-Signature: e1c7b331cb521454e7d22df558880a52 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --0000000000001fcf43062785b6e0 Content-Type: text/plain; charset="UTF-8" Hello! Has anyone here used Containernet with DPDK before? Our use-case is evaluating DPDK-based applications under different network conditions (e.g., lossy links). I've watched this talk https://www.youtube.com/watch?v=KPshkuEPOOU, and I've done pretty extensive research into running DPDK applications in containers for intra-host container networking. (+ thank you to all those who responded to my previous question on this forum!) My understanding is that there are two approaches to DPDK + container networking: - Aggregation: Using VirtIo-User (containers) and vhost-user (backend) which offers a software PMD. This also needs to be connected to a virtual switching infrastructure on the host. - Slicing: Using SR-IOV or similar to give containers direct access to devices. I'm not sure how to reconcile these options with Containernet, both conceptually and in practice. Conceptually: - Does Containernet's OVS /switching provide the appropriate infrastructure for the aggregation option? - Is Containernet even compatible with the VF/slicing option? Can I just build a Containernet node from a DPDK-compatible Dockerfile, set it up with the correct (sliced) PCI addresses, and then connect it to Containernet's emulated network? Would I have to configure anything on the emulated network to make this work? In practice: this seems like a really common use-case (DPDK is specifically mentioned in the original Containernet talk!). However, I can't find any clear guides or images for this, in the Containernet repo or otherwise. Thank you in advance! Thea --0000000000001fcf43062785b6e0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello! Has anyone here used Containernet with DPDK before?= Our use-case is evaluating DPDK-based applications under different network= conditions (e.g., lossy links).=C2=A0

I'v= e watched this talk https://www.youtube.com/watch?v=3DKPshkuEPOOU, and I've done pre= tty extensive research into running DPDK applications in containers for int= ra-host container networking. (+ thank you to all those who responded to my= previous question on this forum!)

My understandin= g is that there are two approaches to DPDK=C2=A0+ container networking:=C2= =A0
  • Aggregation: Using VirtIo-User (containers) and vhost= -user (backend) which offers a software PMD. This also needs to be connecte= d to a virtual switching infrastructure on the host.=C2=A0
  • Slicing:= Using SR-IOV or similar to give containers direct access to devices.=C2=A0=
I'm not sure how to reconcile=C2=A0these options with Co= ntainernet, both conceptually and in practice.
=
Conceptually:=C2=A0
  • Does Containernet'= s=C2=A0OVS/switching= =C2=A0provide the appropriate infrastructure for the aggregation option?
  • Is Containernet even compatible with the VF/slicing option? Can I jus= t build a Containernet node from a DPDK-compatible Dockerfile, set it up wi= th the correct (sliced) PCI addresses, and then connect it to Containernet&= #39;s emulated network? Would I have to configure anything on the emulated = network to make this work?=C2=A0
In practice: this seems like= a really common use-case (DPDK is specifically mentioned in the original C= ontainernet talk!). However, I can't find any clear guides or images fo= r this, in the Containernet repo or otherwise.=C2=A0

Thank you in advance!
Thea=C2=A0
--0000000000001fcf43062785b6e0--