Russell Bryant writes:
> On Sun, Aug 6, 2017 at 7:24 AM, Aaron Conole wrote:
>> Russell Bryant writes:
>>
>>> On Fri, Aug 4, 2017 at 1:00 PM, Aaron Conole wrote:
After this commit, users may start a dpdk-enabled ovs setup as a
non-root user. This is accomplished by exporting the $HO
On Sun, Aug 6, 2017 at 7:24 AM, Aaron Conole wrote:
> Russell Bryant writes:
>
>> On Fri, Aug 4, 2017 at 1:00 PM, Aaron Conole wrote:
>>> After this commit, users may start a dpdk-enabled ovs setup as a
>>> non-root user. This is accomplished by exporting the $HOME directory,
>>> which dpdk use
Russell Bryant writes:
> On Fri, Aug 4, 2017 at 1:00 PM, Aaron Conole wrote:
>> After this commit, users may start a dpdk-enabled ovs setup as a
>> non-root user. This is accomplished by exporting the $HOME directory,
>> which dpdk uses to fill in it's semi-persistent RTE configuration.
>>
>> T
On Fri, Aug 4, 2017 at 1:00 PM, Aaron Conole wrote:
> After this commit, users may start a dpdk-enabled ovs setup as a
> non-root user. This is accomplished by exporting the $HOME directory,
> which dpdk uses to fill in it's semi-persistent RTE configuration.
>
> This change may be a bit controve
After this commit, users may start a dpdk-enabled ovs setup as a
non-root user. This is accomplished by exporting the $HOME directory,
which dpdk uses to fill in it's semi-persistent RTE configuration.
This change may be a bit controversial since it modifies /dev/hugepages
as part of starting the
