[dpdk-dev] [PATCH 00/16] nfp: add pf support

Ferruh Yigit ferruh.yigit at intel.com
Mon Aug 28 18:42:33 CEST 2017


On 8/24/2017 5:20 PM, Alejandro Lucero wrote:
> NFP PMD has just had support for SRIOV VFs until now. This patchset 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 and 
> doing some NFP configuration. This needs 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.
> 
> Alejandro Lucero (16):
>   nfp: add nsp user space interface
>   nfp: add specific pf probe function
>   nfp: add support for new pci id
>   nfp: add nsp support for commands
>   nfp: add nsp fw upload command
>   nfp: add nsp symbol resolution command
>   nfp: add fw upload logic
>   nfp: add support for vnic config bar mapping
>   nfp: add support for vNIC rx/tx bar mappings
>   nfp: support pf devices inside pmd initialization
>   nfp: allocate eth_dev from pf probe function
>   nfp: support pf multiport
>   nfp: add nsp support for hw link configuration
>   nfp: add support for hw port link configuration
>   nfp: read pf port mac addr using nsp
>   doc: update nfp with pf support information

For all patches in the set, can you please run the tool
./devtools/check-git-log.sh [1], it checks for some common commit log
errors.


[1]
./devtools/check-git-log.sh checks the applied commits in the tree and
gets commit number to check as parameter:
"./devtools/check-git-log.sh -16" for this case.



More information about the dev mailing list