From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752427AbeDTUrz (ORCPT ); Fri, 20 Apr 2018 16:47:55 -0400 Received: from merlin.infradead.org ([205.233.59.134]:56368 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751860AbeDTUrx (ORCPT ); Fri, 20 Apr 2018 16:47:53 -0400 Subject: Re: [pci PATCH v8 0/4] Add support for unmanaged SR-IOV To: Alexander Duyck Cc: Alexander Duyck , Bjorn Helgaas , linux-pci@vger.kernel.org, virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org, Netdev , "Daly, Dan" , LKML , linux-nvme@lists.infradead.org, Keith Busch , netanel@amazon.com, Don Dutile , Maximilian Heyne , "Wang, Liang-min" , "Rustad, Mark D" , David Woodhouse , Christoph Hellwig , dwmw@amazon.co.uk References: <20180420162633.46077.49012.stgit@ahduyck-green-test.jf.intel.com> <5fc62d10-790f-2356-c2f6-fd49f542dd3c@infradead.org> From: Randy Dunlap Message-ID: Date: Fri, 20 Apr 2018 13:47:33 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/20/18 13:01, Alexander Duyck wrote: > On Fri, Apr 20, 2018 at 10:23 AM, Randy Dunlap wrote: >> On 04/20/18 09:28, Alexander Duyck wrote: >>> This series is meant to add support for SR-IOV on devices when the VFs are >>> not managed by the kernel. Examples of recent patches attempting to do this >>> include: >>> virto - https://patchwork.kernel.org/patch/10241225/ >>> pci-stub - https://patchwork.kernel.org/patch/10109935/ >>> vfio - https://patchwork.kernel.org/patch/10103353/ >>> uio - https://patchwork.kernel.org/patch/9974031/ >> >> Hi, >> >> Somewhere in this patch series it would be nice to tell us what the heck >> a "PF" is. :) >> >> Thanks. > > Sorry, I was kind of operating on the assumption of everyone > understanding SR-IOV nomenclature. Yes, I understood that. :) > A "PF" is a PCIe Physical Function. When you bring up a PCIe device > that supports SR-IOV it is the device that is there to begin with. > > A "VF" is a PCIe Virtual Function. You could think of as a logical > device that is spawned from the physical function using a combination > of hardware configuration via the SR-IOV block in the PCIe extended > configuration space and kernel/driver features. > > There are also a number of online resources you could use to research > SR-IOV further. Hope that helps to clarify some of this. > > Thanks. Thank you. -- ~Randy