DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/4] NFP PF support based on new CPP interface
Date: Fri, 6 Apr 2018 15:47:40 +0100	[thread overview]
Message-ID: <30ee09ef-57d7-dea1-d034-81f8f0a2a8f4@intel.com> (raw)
In-Reply-To: <802aee06-1bb5-594d-4834-bb7ef7b61813@intel.com>

On 4/6/2018 3:44 PM, Ferruh Yigit wrote:
> On 4/5/2018 3:42 PM, Alejandro Lucero wrote:
>> NFP PMD PF support requires to access the NFP chip for initialization.
>> Current NFP PMD PF support was added based on the NSPU interface. This
>> implies to do initialization through the NSP, a embedded ARM processor
>> which does initialization tasks on demand. The main problem with this
>> approach is it requires to add support for new NSP commands each time
>> a new functionality is required, which does not scale well and it is
>> not really flexible.
>>
>> Using the new CPP user space interface, the PMD can do whatever could
>> be done by the NSP, this is current commands and any new functionality
>> required. This CPP interface allows to access any single chip component
>> facilitating initialization, firmware uploading, firmware debugging or
>> extended stats.
>>
>> The changes just change the PMD PF initialization and do not touch the
>> datapath at all. No performance changes nor PMD functionalities are affected.
>>
>> The initial impact using the new CPP interface is the way firmware upload
>> is handled, which helps the PMD detecting the card type and the firmware file
>> to upload. Future commits will include extended stats and some sort of debug
>> channel.
>>
>> The specific CPP code is contained in the first patch, which has not been
>> splitted up because is completely internal to the NFP functionality. The
>> second patch makes the PMD changes required for using the new interface.
>>
>> v2:
>>  - removing unused reference to zlib.h
>>  - fix build errors
>>  - add SPDX tags in new files
>>  - rebase changes nfp.rst
>>
>> Alejandro Lucero (4):
>>   net/nfp: add NFP CPP support
>>   net/nfp: update PMD for using new CPP interface
>>   doc: update NFP guide
>>   net/nfp: remove files
> 
> Series applied to dpdk-next-net/master, thanks.

btw, some nfp files seems still missing spdx tags, can you please check them?

  reply	other threads:[~2018-04-06 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 14:42 Alejandro Lucero
2018-04-05 14:42 ` [dpdk-dev] [PATCH v2 1/4] net/nfp: add NFP CPP support Alejandro Lucero
2018-04-05 14:42 ` [dpdk-dev] [PATCH v2 2/4] net/nfp: update PMD for using new CPP interface Alejandro Lucero
2018-04-05 14:42 ` [dpdk-dev] [PATCH v2 3/4] doc: update NFP guide Alejandro Lucero
2018-04-05 14:42 ` [dpdk-dev] [PATCH v2 4/4] net/nfp: remove files Alejandro Lucero
2018-04-06 14:44 ` [dpdk-dev] [PATCH v2 0/4] NFP PF support based on new CPP interface Ferruh Yigit
2018-04-06 14:47   ` Ferruh Yigit [this message]
2018-04-09  7:20     ` Alejandro Lucero
  -- strict thread matches above, loose matches on Subject: below --
2018-04-05 14:28 Alejandro Lucero
2018-04-05 14:39 ` Alejandro Lucero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=30ee09ef-57d7-dea1-d034-81f8f0a2a8f4@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=alejandro.lucero@netronome.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).