From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 598617CBF for ; Wed, 6 Sep 2017 18:15:37 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Sep 2017 09:15:27 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,484,1500966000"; d="scan'208";a="1215520638" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.57]) ([10.237.220.57]) by fmsmga002.fm.intel.com with ESMTP; 06 Sep 2017 09:15:26 -0700 To: Alejandro Lucero , dev@dpdk.org References: <1504275141-35448-1-git-send-email-alejandro.lucero@netronome.com> From: Ferruh Yigit Message-ID: Date: Wed, 6 Sep 2017 17:15:25 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <1504275141-35448-1-git-send-email-alejandro.lucero@netronome.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v2 00/18] net/nfp: add PF support 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: Wed, 06 Sep 2017 16:15:38 -0000 On 9/1/2017 3:12 PM, Alejandro Lucero wrote: > NFP PMD has just had support for SRIOV VFs until now. This patch set adds > support for the PF, but just for being used as another DPDK port. No VF > management is added by now. > > NFP is a programmable device and it supports virtual NICs (vNICs) through > firmware implementation. Different firmware applications implement vNICs > for PF devices and VF devices, being number of vNICs dependent on the > firmware and the NFP card available. PF vNIC (virtual) BARs are a subset > of PF PCI device BARs while VF vNIC BARs are same than VF PCI BARs. > > Working with VF vNICs requires a PF driver uploading the firmware, doing > some NFP configuration and creating/destroying VFs. This can be only done > with the kernel NFP PF netdev driver by now. > > Working with PF vNIC requires the PMD doing the NFP configuration and for > accessing the NFP a specific user space interface is created. NFP Service > Processor Userspace (NSPU) interface allows to create specific PCI BAR > windows for accessing different parts of the NFP device, including the > Network Service Processor (NSP) itself. The NSPU interface is implemented > as the base for working with the PF. > > v2: > - fix commits headers > - update nic guide > - add info to release notes > - creating different features files for PF and VF > - fix typo inside nfp_nspu.c > > Alejandro Lucero (18): > net/nfp: add NSP user space interface > net/nfp: add specific PF probe function > net/nfp: add support for new PCI id > net/nfp: add NSP support for commands > net/nfp: add NSP FW upload command > net/nfp: add NSP symbol resolution command > net/nfp: add FW upload logic > net/nfp: add support for vnic config bar mapping > net/nfp: add support for vNIC Rx/Tx bar mappings > net/nfp: support PF devices inside PMD initialization > net/nfp: allocate ethernet device from PF probe function > net/nfp: support PF multiport > net/nfp: add NSP support for HW link configuration > net/nfp: add support for HW port link configuration > net/nfp: read PF port MAC addr using NSP > doc: update NFP with PF support information > doc: update release notes with NFP PF support > doc: create different features files for NFP drivers Series applied to dpdk-next-net/master, thanks. (Except patch 16/18, instead of it applied patch dpdk.org/patch/28425/)