Re: [dpdk-stable] [PATCH 0/2] nfp: support non-root user for the Netronome

[Kevin Traynor <ktraynor@redhat.com>]

On 05/20/2018 08:19 AM, Yuanhan Liu wrote:
> On Mon, May 14, 2018 at 03:23:41PM +0100, Kevin Traynor wrote:
>> Ping Yuanhan - can you clarify question below? Also, can you let us know
> 
> Hi Kevin,
> 
> Sorry for being late: I just have very little time at weekends. I planned
> to handle it last week, but I had to do something else.
> 
> And to your question: yes, they are not pushed yet: I should have done that
> weeks ago though.
> 
> I will push them today.
> 
Hi Yuanhan, thanks - I see them now.

>> when you are planning further backports to 17.11 stable branch?
> 
> I just want to know do you expect something else to be released in 17.11.3?
> If so, could you do a list, just for making sure I don't miss it.
> 

I ran git-log-fixes and it gave a list of 253 post v18.02 fixes in head
of master (not including typo/base drv fixes) that look relevant for
17.11, with another 20 unclear as they are missing 'Fixes:' tag. On the
17.11 branch there's 99 fixes from v17.11.1..HEAD.

There might a few discrepancies in accounting due to different
18.02.0/17.11.1 release dates etc, but at that number it seems like
there are fixes missing - unless they are not suitable for backport for
some other criteria?

I made a list of all fixes that look relevant on master and 17.11
branches, it's quite long, I will send separately.

One unusual case that is needed is a fix for a fix that is not on master
but is on stable branches. The fix is here:
http://dpdk.org/browse/dpdk-stable/commit/?h=18.02&id=e89e323e4ce58f2cbbc7afcc2d5dc7ce66075e81

thanks,
Kevin.

> 	--yliu
>>
>> thanks,
>> Kevin.
>>
>> On 05/08/2018 10:23 AM, Kevin Traynor wrote:
>>> On 05/06/2018 07:34 AM, Yuanhan Liu wrote:
>>>> On Mon, Apr 30, 2018 at 07:02:29PM +0100, Kevin Traynor wrote:
>>>>> On 04/30/2018 06:20 PM, Aaron Conole wrote:
>>>>>> Even when trying to use the Netronome cards via VFIO, there is a
>>>>>> lock file being requested, which requires root access.  This series
>>>>>> fixes an issue with the nfp driver lock release always releasing
>>>>>> 'nfp0' (which isn't a bug in practice for other reasons) as well
>>>>>> as allowing the lock file location to be configured by the application
>>>>>> or user via the HOME environment variable (similar to other resources
>>>>>> in the DPDK framework).
>>>>>>
>>>>>> This series is only applicable to the stable tree because the nfp
>>>>>> driver is completely rewritten for later versions of DPDK.
>>>>>>
>>>>>
>>>>> Hi Yuanhan, I think we would like to get this into the next 17.11 stable
>>>>> release if possible. Not sure when you are merging patches into the tree
>>>>> for it?
>>>>
>>>> Hi,
>>>>
>>>> I have just applied it to dpdk-stable/17.11. It will be part of 17.11.3
>>>> LTS release.
>>>>
>>>
>>> Hi,
>>>
>>> They don't appear to be on the branch? Maybe you have a private 'next'
>>> branch or something in your workflow, but reporting in case something
>>> still needs to be pushed.
>>>
>>> thanks,
>>> Kevin.
>>>
>>>> Thanks.
>>>>
>>>> 	--yliu
>>>>>
>>>>> Kevin.
>>>>>
>>>>>> Aaron Conole (2):
>>>>>>   nfp: unlink the appropriate lock file
>>>>>>   nfp: allow for non-root user
>>>>>>
>>>>>>  drivers/net/nfp/nfp_nfpu.c | 25 +++++++++++++++++++++----
>>>>>>  1 file changed, 21 insertions(+), 4 deletions(-)
>>>>>>
>>>