From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 270B7376C for ; Wed, 2 Dec 2015 17:32:00 +0100 (CET) Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (Postfix) with ESMTPS id 248EA1B402F; Wed, 2 Dec 2015 16:31:59 +0000 (UTC) Received: from redhat.com (vpn1-4-19.ams2.redhat.com [10.36.4.19]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with SMTP id tB2GVsOU018072; Wed, 2 Dec 2015 11:31:55 -0500 Date: Wed, 2 Dec 2015 18:31:53 +0200 From: "Michael S. Tsirkin" To: Thomas Monjalon Message-ID: <20151202182704-mutt-send-email-mst@redhat.com> References: <20151028211309.14155.23867.stgit@gimli.home> <564A0E70.4030409@scylladb.com> <1449070123.15753.35.camel@redhat.com> <1473285.yZJWhu9CPo@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1473285.yZJWhu9CPo@xps13> X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 Cc: Avi Kivity , gleb@scylladb.com, corbet@lwn.net, dev@dpdk.org, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, Alex Williamson , hjk@hansjkoch.de Subject: Re: [dpdk-dev] [PATCH] vfio: Include No-IOMMU mode X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Dec 2015 16:32:00 -0000 On Wed, Dec 02, 2015 at 05:19:18PM +0100, Thomas Monjalon wrote: > Hi, > > 2015-12-02 08:28, Alex Williamson: > > On Mon, 2015-11-16 at 19:12 +0200, Avi Kivity wrote: > > > On 11/16/2015 07:06 PM, Alex Williamson wrote: > > > > FYI, this is now in v4.4-rc1 (the slightly modified v2 version). I want > > > > to give fair warning though that while we seem to agree on this idea, it > > > > hasn't been proven with a userspace driver port. I've opted to include > > > > it in this merge window rather than delaying it until v4.5, but I really > > > > need to see a user for this before the end of the v4.4 cycle or I think > > > > we'll need to revert and revisit for v4.5 anyway. I don't really have > > > > any interest in adding and maintaining code that has no users. Please > > > > keep me informed of progress with a dpdk port. Thanks, > > > > > > Thanks Alex. Copying the dpdk mailing list, where the users live. > > > > > > dpdk-ers: vfio-noiommu is a replacement for uio_pci_generic and > > > uio_igb. It supports MSI-X and so can be used on SR/IOV VF devices. > > > The intent is that you can use dpdk without an external module, using > > > vfio, whether you are on bare metal with an iommu, bare metal without an > > > iommu, or virtualized. However, dpdk needs modification to support this. > > > > Still no users for this that I'm aware of. I'm going to revert this in > > rc5 unless something changes. Thanks, > > Removing needs for out-of-tree modules is a really nice achievement. > Yes, we (in the DPDK project) should check how to use this no-iommu VFIO > and to replace igb_uio. > > I'm sorry we failed to catch your email and follow up. > Is it really too late? What is the risk of keeping it in Linux 4.4? > Advertising a new feature and removing it would be frustrating. > > Have you tried this VFIO mode with DPDK? > How complex would be the patch to support it? > > Thanks These things need to be developed together, one can't be sure it meets userspace needs if no one tried. And then where would we be? Supporting a broken interface forever. If someone writes the userspace code, then this feature can come back for 4.5. -- MST