2016-12-22 3:05 GMT-08:00 Kevin Traynor :
> On 12/22/2016 10:02 AM, Kevin Traynor wrote:
>> On 12/21/2016 07:35 PM, Daniele Di Proietto wrote:
>>> 2016-12-21 10:18 GMT-08:00 Kevin Traynor :
On 12/21/2016 03:02 AM, Daniele Di Proietto wrote:
>
On 12/22/2016 10:02 AM, Kevin Traynor wrote:
> On 12/21/2016 07:35 PM, Daniele Di Proietto wrote:
>> 2016-12-21 10:18 GMT-08:00 Kevin Traynor :
>>> On 12/21/2016 03:02 AM, Daniele Di Proietto wrote:
2016-12-20 14:08 GMT-08:00 Kevin Traynor :
> On
On 12/21/2016 07:35 PM, Daniele Di Proietto wrote:
> 2016-12-21 10:18 GMT-08:00 Kevin Traynor :
>> On 12/21/2016 03:02 AM, Daniele Di Proietto wrote:
>>> 2016-12-20 14:08 GMT-08:00 Kevin Traynor :
On 12/15/2016 11:54 AM, Ciara Loftus wrote:
>
2016-12-21 10:18 GMT-08:00 Kevin Traynor :
> On 12/21/2016 03:02 AM, Daniele Di Proietto wrote:
>> 2016-12-20 14:08 GMT-08:00 Kevin Traynor :
>>> On 12/15/2016 11:54 AM, Ciara Loftus wrote:
'dpdk' ports no longer have naming restrictions. Now, instead
On 12/21/2016 03:02 AM, Daniele Di Proietto wrote:
> 2016-12-20 14:08 GMT-08:00 Kevin Traynor :
>> On 12/15/2016 11:54 AM, Ciara Loftus wrote:
>>> 'dpdk' ports no longer have naming restrictions. Now, instead of
>>> specifying the dpdk port ID as part of the name, the PCI
On 12/15/2016 11:54 AM, Ciara Loftus wrote:
> 'dpdk' ports no longer have naming restrictions. Now, instead of
> specifying the dpdk port ID as part of the name, the PCI address of the
> device must be specified via the 'dpdk-devargs' option. eg.
>
> ovs-vsctl add-port br0 my-port
> ovs-vsctl set
'dpdk' ports no longer have naming restrictions. Now, instead of
specifying the dpdk port ID as part of the name, the PCI address of the
device must be specified via the 'dpdk-devargs' option. eg.
ovs-vsctl add-port br0 my-port
ovs-vsctl set Interface my-port type=dpdk
ovs-vsctl set Interface