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 53D0AE07 for ; Mon, 30 Apr 2018 20:02:33 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id E811476FBA; Mon, 30 Apr 2018 18:02:32 +0000 (UTC) Received: from ktraynor.remote.csb (unknown [10.36.118.53]) by smtp.corp.redhat.com (Postfix) with ESMTP id 6CA29215CDAA; Mon, 30 Apr 2018 18:02:30 +0000 (UTC) To: Aaron Conole , stable@dpdk.org Cc: Alejandro Lucero , Ferruh Yigit , Yuanhan Liu , Eelco Chaudron , Pablo Cascon , Adrien Mazarguil References: <20180430172040.13506-1-aconole@redhat.com> From: Kevin Traynor Organization: Red Hat Message-ID: Date: Mon, 30 Apr 2018 19:02:29 +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: <20180430172040.13506-1-aconole@redhat.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.6 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.1]); Mon, 30 Apr 2018 18:02:32 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.1]); Mon, 30 Apr 2018 18:02:32 +0000 (UTC) for IP:'10.11.54.6' DOMAIN:'int-mx06.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: Mon, 30 Apr 2018 18:02:34 -0000 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? 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(-) >