From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f46.google.com (mail-pg0-f46.google.com [74.125.83.46]) by dpdk.org (Postfix) with ESMTP id 11FF32B9C for ; Mon, 2 Jan 2017 20:47:17 +0100 (CET) Received: by mail-pg0-f46.google.com with SMTP id y62so154404026pgy.1 for ; Mon, 02 Jan 2017 11:47:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=K4q7krWUJ5HpPp/HOdKHH2D3YMjd6BIyqn6pRKZfh3s=; b=eujCs47xfSSBvm0GTLd6Hk4SmpJV2079LeyVZ6CTEMVopTtM054Mo3mzJ2woXIfFvN xspRvIBeHfH2P7IK8laTV6HfoCStTg1Ch26eFkwxVHaZULzd5Gt4bE/ABBNEgDZpu+Rn 07B2mljAUw8lK2M7rUZ+vhF4NnI7V6abwjceJOe03vmIwY45ntV9aADmPwSsfz9m2ip/ jct0IZ9FpRDB8L3hCF0U5aX8KhUwtGp/zdtWQfCqtYw6ls7E2HBU6C432ykuN21jJv7B 4STmh+ZjBMkVRjoojsvvRwDVgowVfgVZUEQ1vFXkm4P4hLE17J5KJwdu4J6bm3BeLCbQ mYkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=K4q7krWUJ5HpPp/HOdKHH2D3YMjd6BIyqn6pRKZfh3s=; b=UsWo9FUOJh6Qlh6ZqM88WqXopS8JzJiji+5StzRv6P6Rrf29CQdmB74elLOmrLZhTq G+5IoKICIOJmzg0Ew8PXgBtULDQp2+U80NEKBYNG0XpFwQK1ul9623OLxnRk2Hsx6lTp RrAG7V/4QZC8aUvSq7OcOKuv/aUYrHdrNF0MToh+qr9i0Q1g5rVFYZipORuJ5SiQQEhF qhcE+g38r6kJGBSEVrd+Dp1C3LO69bU29zJrZOJemTM9FjXDJxb4eTSBqwkHqVJ0kalu liHu6BYz8gwbqmeAuZuM8pL9D8B+9X6BfU6ZWIk4pVbZCMyfo6KdNc0mYPf9YNvC3VVo Msgw== X-Gm-Message-State: AIkVDXITlBtLTyv7rw17tssbgqRU9oV9S002kA0gJasGMGghsAHKWSd5jEstSh7yK4Y6pg== X-Received: by 10.84.218.133 with SMTP id r5mr129220117pli.175.1483386436615; Mon, 02 Jan 2017 11:47:16 -0800 (PST) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id x4sm135224554pgc.14.2017.01.02.11.47.16 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 02 Jan 2017 11:47:16 -0800 (PST) Date: Mon, 2 Jan 2017 11:47:09 -0800 From: Stephen Hemminger To: Thomas Monjalon Cc: "Walker, Benjamin" , dev@dpdk.org Message-ID: <20170102114709.0a2f5546@xeon-e3> In-Reply-To: <30911426.SrBqgP6jBN@xps13> References: <1483044080.11975.1.camel@intel.com> <20161229171453.57a4326a@xeon-e3> <30911426.SrBqgP6jBN@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] Running DPDK as an unprivileged user X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2017 19:47:18 -0000 On Mon, 02 Jan 2017 15:32:08 +0100 Thomas Monjalon wrote: > 2016-12-29 17:14, Stephen Hemminger: > > On Thu, 29 Dec 2016 20:41:21 +0000 > > "Walker, Benjamin" wrote: > > > My second question is whether the user should be allowed to > > > mix uio and vfio usage simultaneously. For vfio, the > > > physical addresses are really DMA addresses and are best > > > when arbitrarily chosen to appear sequential relative to > > > their virtual addresses. For uio, they are physical > > > addresses and are not chosen at all. It seems that these two > > > things are in conflict and that it will be difficult, ugly, > > > and maybe impossible to resolve the simultaneous use of > > > both. > > > > Unless application is running as privileged user (ie root), UIO > > is not going to work. Therefore don't worry about mixed environment. > > Yes, mixing UIO and VFIO is possible only as root. > However, what is the benefit of mixing them? One possible case where this could be used, Hyper-V/Azure and SR-IOV. The VF interface will show up on an isolated PCI bus and the virtual NIC is on VMBUS. It is possible to use VFIO on the PCI to get MSI-X per queue interrupts, but there is no support for VFIO on VMBUS.