From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by dpdk.org (Postfix) with ESMTP id A5F0D1D9E for ; Tue, 22 May 2018 12:45:13 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id A9D6A81FE163; Tue, 22 May 2018 10:45:12 +0000 (UTC) Received: from ktraynor.remote.csb (ovpn-117-162.ams2.redhat.com [10.36.117.162]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5D67C2026990; Tue, 22 May 2018 10:45:10 +0000 (UTC) From: Kevin Traynor To: Yuanhan Liu Cc: Aaron Conole , stable@dpdk.org, Alejandro Lucero , Ferruh Yigit , Eelco Chaudron , Pablo Cascon , Adrien Mazarguil , Thomas Monjalon References: <20180430172040.13506-1-aconole@redhat.com> <20180506063438.tgp7oso4gj5qnng4@yuanhanliu-NB0.tencent.com> <6d5445c2-682b-1fe2-df7a-0be25c0596bf@redhat.com> <20180520071926.pmplwd322rbcrng3@yuanhanliu-NB0.tencent.com> Organization: Red Hat Message-ID: Date: Tue, 22 May 2018 11:45:09 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <20180520071926.pmplwd322rbcrng3@yuanhanliu-NB0.tencent.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Tue, 22 May 2018 10:45:12 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Tue, 22 May 2018 10:45:12 +0000 (UTC) for IP:'10.11.54.4' DOMAIN:'int-mx04.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'ktraynor@redhat.com' RCPT:'' Subject: Re: [dpdk-stable] [PATCH 0/2] nfp: support non-root user for the Netronome X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2018 10:45:14 -0000 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(-) >>>>>> >>>