Sergio Gonzalez Monroy writes:
> On 02/08/2017 16:07, Aaron Conole wrote:
>> Sergio Gonzalez Monroy writes:
>>
>>> Hi Aaron,
>> Hi Sergio,
>>
>>> On 01/08/2017 23:05, Aaron Conole wrote:
After this commit, users may start a dpdk-enabled ovs setup as a
non-root user. This is accomplish
On 02/08/2017 16:07, Aaron Conole wrote:
Sergio Gonzalez Monroy writes:
Hi Aaron,
Hi Sergio,
On 01/08/2017 23:05, 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 f
Sergio Gonzalez Monroy writes:
> Hi Aaron,
Hi Sergio,
> On 01/08/2017 23:05, 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 c
Hi Aaron,
On 01/08/2017 23:05, 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 controversial si
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
