[dpdk-dev] [dpdk-stable] [RFC 2/2] nfp: allow for non-root user
Aaron Conole
aconole at redhat.com
Fri Apr 20 16:56:06 CEST 2018
Ferruh Yigit <ferruh.yigit at intel.com> writes:
> On 4/19/2018 7:05 AM, Alejandro Lucero wrote:
>> On Wed, Apr 18, 2018 at 1:32 PM, Aaron Conole <aconole at redhat.com> wrote:
>>
>>> Alejandro Lucero <alejandro.lucero at netronome.com> writes:
>>>
>>>> On Tue, Apr 17, 2018 at 8:19 PM, Aaron Conole <aconole at redhat.com>
>>> wrote:
>>>>
>>>> Alejandro Lucero <alejandro.lucero at netronome.com> writes:
>>>>
>>>> > I was just wondering, if device device PCI sysfs resource files or
>>> VFIO group /dev files
>>>> require to change
>>>> > permissions for non-root users, does it not make sense to adjust also
>>> /var/lock in the
>>>> system?
>>>>
>>>> For the /dev, we use udev rules - so the correct individual vfio device
>>>> files get assigned the correct permissions. No such mechanism exists
>>>> for /var/lock as far as I can tell.
>>>>
>>>> Ex. see:
>>>>
>>>> https://github.com/openvswitch/ovs/blob/master/
>>> rhel/usr_lib_udev_rules.d_91-vfio.rules
>>>>
>>>>
>>>> Maybe something similar exists that we could use to generate the lock
>>>> file automatically?
>>>>
>>>> What about /sysfs/bus/pci/device/$PCI_DEV/resource file?
>>>>
>>>> Is RH forcing OVS DPDK to only work if the host has IOMMU support?
>>>
>>> Yes.
>>>
>>
>> Ok then. It makes sense now to apply this patch to stable versions.
>>
>> Acked-by: Alejandro Lucero <alejandro.lucero at netronome.com>
>
> Since the target is the stable tree, I will drop them from patchwork as not
> applicable.
>
> Can you please send v1 of the patch to the stable mail list, it can be good idea
> to cc stable maintainers as well.
Will do. I'll spin into a proper series and submit next week.
Sorry for the extra noise, Ferruh.
More information about the dev
mailing list