Daniele Di Proietto writes:
> On 02/02/2017 12:48, "Ben Pfaff" wrote:
>
>>On Tue, Jan 24, 2017 at 06:21:53PM -0800, Daniele Di Proietto wrote:
>>> Names like dpdk0 and dpdk1 are not enough to identify a DPDK interface.
>>> We could update README.RHEL.rst and add
>>>
>>> OVS_EXTRA='set Interface
On Sat, Feb 11, 2017 at 12:14:24AM +, Daniele Di Proietto wrote:
> On 02/02/2017 12:48, "Ben Pfaff" wrote:
> >I don't understand why this uses "set" then $1. Are you concerned that
> >BOND_DPDK_DEVARGS might have multiple words and you want to get just the
> >first one?
>
> Now for each inte
On 02/02/2017 12:48, "Ben Pfaff" wrote:
>On Tue, Jan 24, 2017 at 06:21:53PM -0800, Daniele Di Proietto wrote:
>> Names like dpdk0 and dpdk1 are not enough to identify a DPDK interface.
>> We could update README.RHEL.rst and add
>>
>> OVS_EXTRA='set Interface ${DEVICE} options:dpdk-devargs=0
On Tue, Jan 24, 2017 at 06:21:53PM -0800, Daniele Di Proietto wrote:
> Names like dpdk0 and dpdk1 are not enough to identify a DPDK interface.
> We could update README.RHEL.rst and add
>
> OVS_EXTRA='set Interface ${DEVICE} options:dpdk-devargs=:01:00.0'
>
> but a better solution is to add ne
Names like dpdk0 and dpdk1 are not enough to identify a DPDK interface.
We could update README.RHEL.rst and add
OVS_EXTRA='set Interface ${DEVICE} options:dpdk-devargs=:01:00.0'
but a better solution is to add new parameters in the configuration file
to explicitly specify the dpdk-devargs.
F
