On Wed, Apr 11, 2018 at 08:14:07PM -0400, Flavio Fernandes wrote:
>
>
> > On Apr 7, 2018, at 1:53 PM, Ben Pfaff wrote:
> >
> > On Fri, Apr 06, 2018 at 04:18:31PM -0400, Flavio Fernandes wrote:
> >> Dear OVS Gurus:
> >>
> >> I came across something simple and silly, which is
Hello,
On the following setup, where all cores but 0 are isolated,
available: 2 nodes (0-1)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9
node 1 cpus: 10 11 12 13 14 15 16 17 18 19
I am trying to start OVS entirely on numa node 1 as following
ovs-vsctl --no-wait set Open_vSwitch .
> On Apr 7, 2018, at 1:53 PM, Ben Pfaff wrote:
>
> On Fri, Apr 06, 2018 at 04:18:31PM -0400, Flavio Fernandes wrote:
>> Dear OVS Gurus:
>>
>> I came across something simple and silly, which is making me think it is
>> actually a bug.
>>
>> In a nutshell, I'm trying to use a
I'am not a user of OpenVSwitch, but thought I could drop this question
here. I hope there is some knowledge here that could explain the
behaviour of the problem I have.
I have a linux bridge configured like this:
Where I can ping from BR0 to 172.16.1.y
Where I can ping from BR0 to
On 04/10/2018 11:12 AM, Stokes, Ian wrote:
-Original Message-
From: Ilya Maximets [mailto:i.maxim...@samsung.com]
Sent: Monday, 29 January, 2018 09:35
To: Jan Scheurich ; Venkatesan Pradeep
; Stokes, Ian
> One of the OVS-DPDK maintainers will have to speak up about the flow
> control messages. I don't know.
Hi Michael,
can you provide the following to help debug this:
OVS Version.
DPDK Version.
NIC Model.
pmd-cpu-mask.
lcore mask.
Port configuration for all ports (including flow control, queue