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 E18E045D48 for ; Tue, 19 Nov 2024 23:14:20 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6FF404025D; Tue, 19 Nov 2024 23:14:20 +0100 (CET) Received: from fhigh-a1-smtp.messagingengine.com (fhigh-a1-smtp.messagingengine.com [103.168.172.152]) by mails.dpdk.org (Postfix) with ESMTP id C3DE54021F for ; Tue, 19 Nov 2024 23:14:19 +0100 (CET) Received: from phl-compute-06.internal (phl-compute-06.phl.internal [10.202.2.46]) by mailfhigh.phl.internal (Postfix) with ESMTP id 1A8DC1140105; Tue, 19 Nov 2024 17:14:19 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-06.internal (MEProxy); Tue, 19 Nov 2024 17:14:19 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1732054459; x=1732140859; bh=KDSJxFtGop5Oaq36k0JzKZoBENXvMWTRgHZ+sj0U/U4=; b= OBD0B8Emqz0URukFGaUiuIsI2HBwy07PXJxgEH4YzTldedN/8VPdpJ+f8DLd0pZJ 0DJLAmenEKTn2FhNa5eU2ZI7cskavFS20/HivqVGBSrL7fWWVbY9v2JDzTwGbxeU YAWGp9fXM2AGkWwP8SFKeUPiwgeKslP5gbw4OLDnfZSVNRg69ponuKusD5ixq2d3 hUPX+ZDTN2VSqA0pBlxl4eTdBq8goDgCiK076oSPXGa/K7NBOrskfZSPlYYpfB36 VlAF5sZs2uWa5B5dzzL6N4hF6qGP0t5GuTrwuaq5MGhZdh4b8uBuDBjX7YKJ/lat yftOoIbXkaHCB4+fPT9PTQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1732054459; x= 1732140859; bh=KDSJxFtGop5Oaq36k0JzKZoBENXvMWTRgHZ+sj0U/U4=; b=Y jy3ocUWzMnz16loqhNdRcrD4ch9bzd3JvIvyO3NvdoaeX6MBnEhthk4Cv7WKejqj tWNQlUyku2LrSllhUTH1fbFt4AwDa5hHAbUDs8bKorQG0hi3SYusLZvli9Pi+4ut kc5FK5Uj/v5BFTtDN45Zm+UM/ZCadu4Ai8UcEptCG3/YDSnwa+uZam5/A8YvaiW9 WhGdnvskjlc2zSsQ3qCQF0uI4VmwkbRcINJIv3tZbD+1RKJAy36MViff3KNXCMro TkEoKXa2sH0wl/j3k/URGka599V5cz0YnBunMwSWXDax3/7TQRwlhMPW+7CM9WX6 oU6Bo+vH8TLhw2ANugXyg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrfedvgdduheeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnh htshculddquddttddmnecujfgurhephffvvefufffkjghfggfgtgesthfuredttddtjeen ucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrg hlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpeejudevheeiveduuddtveffgfdtgeek ueevjeffjeegtdeggeekgfdvuefgfeekjeenucevlhhushhtvghrufhiiigvpedtnecurf grrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtpdhn sggprhgtphhtthhopeefpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopehthhgvrg drrhhoshhsmhgrnhestghsrdhsthgrnhhfohhrugdrvgguuhdprhgtphhtthhopehsthgv phhhvghnsehnvghtfihorhhkphhluhhmsggvrhdrohhrghdprhgtphhtthhopehushgvrh hsseguphgukhdrohhrgh X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 19 Nov 2024 17:14:18 -0500 (EST) From: Thomas Monjalon To: Thea Corinne Rossman Cc: stephen@networkplumber.org, users@dpdk.org Subject: Re: Containernet (Docker/Container Networking) with DPDK? Date: Tue, 19 Nov 2024 23:14:16 +0100 Message-ID: <2390764.BjyWNHgNrj@thomas> In-Reply-To: References: <20241119132903.12fefa8c@hermes.local> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" 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 19/11/2024 22:39, Thea Corinne Rossman: > This is SO helpful -- thank you so much. > > One follow-up question regarding NICs: can multiple containers on the same > host share the same PCI device? If I have a host NIC with (say) VFIO driver > binding, do I have to split it with some kind of SR-IOV so that each > container has its own "NIC" binding? Or, when running DPDK's "devbind" > script, can I set up each one with the same PCI address? You need to split devices. SR-IOV VF may help, or you can use SF which was designed exactly for this, with the help of the Linux auxiliary bus.