From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 29E45A0563 for ; Thu, 27 Feb 2020 21:50:07 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 773272C02; Thu, 27 Feb 2020 21:50:06 +0100 (CET) Received: from mail-qk1-f178.google.com (mail-qk1-f178.google.com [209.85.222.178]) by dpdk.org (Postfix) with ESMTP id 4AA0F1F1C for ; Thu, 27 Feb 2020 21:50:04 +0100 (CET) Received: by mail-qk1-f178.google.com with SMTP id m9so841167qke.4 for ; Thu, 27 Feb 2020 12:50:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=OusuW8td0x4rSxHhw5HNibuw7NgLhJZAUoX+oVpaH2Y=; b=iD4H91wsCBQ1OUCgZ++s6QRzoGcTeqgqvKdPAZvr2Dwq8ue9YcUoVINtJI8QVdOpFk uxBZMQL3HGk+ap8qMVmyn9Z7jSrD8Kq52s71h4lncpgcbONogsWw4djiASYs/oXEtCM6 u5LTv1UWAhkcDT3YfIl1uLAvzSte2bxBVXVEYx5/OVJsmpdqG8fGKgyAfjsDDyBVChv1 +9PFl4xwXM9qf2KragfKr/kWNzjG/dNsUydozfCq8b19qgVauRsvITW7cXy9F0PboOnk t8Z1HzaqkTD0rAAHIo2l11FtEkLklkiBMhTfFn+692Q2mLvYTVTmDN8Ok5ggCunp1HSA hKsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=OusuW8td0x4rSxHhw5HNibuw7NgLhJZAUoX+oVpaH2Y=; b=KiR+nv/ZWLKoii2VP28NARYUvJxoecGJOCVuVgAkbpDqxIDT6QJJMz0KsbEzzt1ejT XKwIMHT6rbXnGci71frmdmOYouaQryNeF2wgyMVgZizFa9pfXC57pPDseHrsSg+DxcN6 aN8t54xgXOijmiEejfO6a1JuZUVFDSQf8Af1imiZ8U53FiT0PseSPjQWcl4ZFEPV7ELf K6Bzt7CJQCRbZzn/cDwO/HcNUjns5SEGq169CFFZnLenNd4LpAyYgECsj6J0HTWd0VDa JrAuTpqEe5ovFnLOfa7T5tcDAWaIdvVDh+YenETzyE1gqRFBGfMawaZa8StMijnJkOZb B2EQ== X-Gm-Message-State: APjAAAXxOnHNLzMgGUHFcVpx1DI/TIL2wO1uklFZh8IMfF7ws+ytDn1t 5LrSlc0StSFxcv/tXd8hZ8dWnWZOj4GG6jBYnZQgsLau X-Google-Smtp-Source: APXvYqyrKy8UzfYFt0F7ZG5r3TkwekJOXyh4JmFUq115Kpt/q4EAtYPc7rQTtxGllcEo6O3+CddHv/nd1v9PM28+SmY= X-Received: by 2002:a37:4e89:: with SMTP id c131mr1415455qkb.5.1582836603382; Thu, 27 Feb 2020 12:50:03 -0800 (PST) MIME-Version: 1.0 From: Staffan Wiklund Date: Thu, 27 Feb 2020 21:49:52 +0100 Message-ID: To: users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] How to access SR-IOV devices from a DPDK application executing in a Docker container? X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hello I wonder if you please can help me with a question related to execution of a DPDK application in a Docker container? In the DPDK documentation, Programmer's Guide, HowTo Guide, chapter 7, it says among other things "There are two use models of running DPDK inside containers, as shown in Fig. 7.1" Figure 7.1 shows two use models of running DPDK in a container. The first use model is called "slicing" where a DPDK application in a container access an SR-IOV device directly without using vSwitch or vRouter. I wonder if you please can describe how this can be accomplished? I wonder: 1. Are there any specific requirements on the container so that it contains for example certain device drivers or fulfills any other specific requirement? 2. If the PCI address of the SR-IOV VF device as seen in the host is provided to the DPDK application in the container, can this application access the SR-IOV VF device? 3. Is there anything else that is needed to make it possible for a DPDK application in a Docker container to communicate via an SR-IOV VF device in the host? Thanks in advance for your help Staffan