From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-f170.google.com (mail-io0-f170.google.com [209.85.223.170]) by dpdk.org (Postfix) with ESMTP id 0B29F8DB3 for ; Thu, 14 Jan 2016 07:03:35 +0100 (CET) Received: by mail-io0-f170.google.com with SMTP id 1so395811491ion.1 for ; Wed, 13 Jan 2016 22:03:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JF2qHkOVWOHdsxkAHJ2Tdro9J+TjQuG9SMHVdxk0rWc=; b=bhTW5PzORgbq8xGFcPbOo3qmlGUBVfQFIq3V+RHIboO396qd6QUjJrX4SrzpEiqFZK Dc0NExqg8FijM1fo9Rr3xtLchIPHHrDHek6uBZ+k9OLW1RSJdVcel6ztb+TQgHc88phc US4Ml5+VkJzRMn+anq4+DuLZtmCShOdPyZ5o49fF0OrPbTp/0X4doRzQlWp0fyLHS7bm o4klzhK3lYhekgsr9RaZfOY8Z+Y+vQcT1y8gff7gn/35CGpF0SiH2YrVXyOEzRB4fV/8 w2dltarX0HTsjRVOf5y0Ox5+66JAqRiS8ku3SRogS6gIvlIV1Noe1yAiHYTHJEEMlfu5 oqKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=JF2qHkOVWOHdsxkAHJ2Tdro9J+TjQuG9SMHVdxk0rWc=; b=D2A2T4L0eV0Rk4/rIaLADCf8TueG3g57azj8XCenxdD55Od1pNoUO8cRcJtuhhQ2ev Z6EQcWqqXmcF73z5BgLRyJdyqJMI2DiMgmPGhHlVk8PEfbbtBX7nvGczmCX/aYToHrKs xx5ahIyEZY+heZq5j1x8on4dN/u5h/SW3ppY9u3JaJ5QqAR5/Z3Eu8a92NbAqjy+5o35 X45lrk5yUUT7P65p/rkB58vshIt6z6ebFdawwcU9Iqa7288h8CV/+sUBbI7E3/JlR7Go Y2dE87YVHaTQOg3LehFTjBkt7J7QbTVp4YfU9xUCsrYnr5ny2tKqGhQVfLE1mNkZtS2+ 1HnA== X-Gm-Message-State: ALoCoQkrrdEL2bwi5lsbf7mFH0o0cYVNmb+VuiseCKjTHK0B8SXkIe/DTrMXyBlswVTnzubuFIpOlUSU+qEeTZPZ0/combBUyg== MIME-Version: 1.0 X-Received: by 10.107.8.135 with SMTP id h7mr3025855ioi.93.1452751414514; Wed, 13 Jan 2016 22:03:34 -0800 (PST) Received: by 10.64.102.229 with HTTP; Wed, 13 Jan 2016 22:03:34 -0800 (PST) In-Reply-To: <1450240711.2674.11.camel@redhat.com> References: <60420822.AbcfvjLZCk@xps13> <566B4A50.9090607@6wind.com> <1449874953.20509.6.camel@redhat.com> <26FA93C7ED1EAA44AB77D62FBE1D27BA6747CE55@IRSMSX108.ger.corp.intel.com> <1450198398.6042.32.camel@redhat.com> <20151216040408.GA18363@sivlogin002.ir.intel.com> <1450240711.2674.11.camel@redhat.com> Date: Thu, 14 Jan 2016 14:03:34 +0800 Message-ID: From: Jike Song To: Alex Williamson Content-Type: text/plain; charset=UTF-8 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] VFIO no-iommu 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: Thu, 14 Jan 2016 06:03:35 -0000 On Wed, Dec 16, 2015 at 12:38 PM, Alex Williamson wrote: > > So it works. Is it acceptable? Useful? Sufficiently complete? Does > it imply deprecating the uio interface? I believe the feature that > started this discussion was support for MSI/X interrupts so that VFs > can support some kind of interrupt (uio only supports INTx since it > doesn't allow DMA). Implementing that would be the ultimate test of > whether this provides dpdk with not only a more consistent interface, > but the feature dpdk wants that's missing in uio. Thanks, > Hi Alex, Sorry for jumping in. Just being curious, how does VFIO No-IOMMU mode support DMA from userspace drivers? If I understand correctly, due to the absence of IOMMU, pcidev has to use physaddr to start a DMA transaction, but how it is supposed to get physaddr from userspace drivers, /proc//pagemap or something else? -- Thanks, Jike