You can use multicast forwarding. Because NDP are unicast and multicast
packets.
Thomas Goirand 于2019年9月10日周二 下午10:09写道：
> Hi Ben and others,
>
> I just want to know: does OVS 2.10 has support for IPv6 mac learning /
> NDP, so that we can avoid the ipv6 broadcast storm in our cloud?
>
> Cheers,
On Tue, Sep 10, 2019 at 04:02:36PM +0200, Thomas Goirand wrote:
> I just want to know: does OVS 2.10 has support for IPv6 mac learning /
> NDP, so that we can avoid the ipv6 broadcast storm in our cloud?
Hi Thomas.
MAC learning is an L2 feature that applies to IPv4 and IPv6 in the
same way. All
Hi Numan,
Thanks for calling out the failure.
Fixed the same in v5.
Did not realize that we have removed OVS tests from repo, hence based on test
number, I ruled it out as an unrelated tests.
Regards,
Ankur
From: Numan Siddique
Sent: Tuesday, September 10, 2019 12:51 AM
To: Ankur Sharma
Cc:
During E-W routing for vlan backed networks, we replace router port
mac with chassis mac, when packet leaves the source hypervisor.
As a result, the destination VM (on remote hypervisor) will see
chassis mac as source mac in received packet.
Although, functionality wise this does not cause any is
On Fri, Sep 6, 2019 at 5:08 PM Mark Michelson wrote:
>
> This document serves to provide an explanation for how OVN will remain
> compatible with OVS. It provides instructions for OVN contributors for
> how to maintain compatibility even across older versions of OVS when
> possible.
>
> Note that
For the series,
Acked-by: Mark Michelson
On 9/10/19 3:42 AM, nusid...@redhat.com wrote:
From: Numan Siddique
Now that OVN has it's own rundir, "ovs-appctl -t ovn-controller/ovn-northd"
doesn't work. To fix this, ovn-appctl utility is added which
looks for the OVN pid/ctl files in the ovn rund
-Original Message-
From: Ilya Maximets
Sent: 10 September 2019 19:29
To: Sriram Vatala ; ovs-dev@openvswitch.org
Cc: ktray...@redhat.com; ian.sto...@intel.com
Subject: Re: [PATCH v8] netdev-dpdk:Detailed packet drop statistics
On 08.09.2019 19:01, Sriram Vatala wrote:
> OVS may be unable
Add empty load balancer controller_event support to logical router
pipeline. Update northd documentation even for logical switch pipeline
Signed-off-by: Lorenzo Bianconi
---
Changes since v2:
- improve code readability
Changes since v1:
- rebase on-top of current ovn master branch
---
northd/ovn
Hi Eelco,
Thanks for the review.
On Tue, Sep 10, 2019 at 7:24 AM Eelco Chaudron wrote:
>
> Hi William,
>
> One comment below, but I’m also wondering if we should warn/log a
> message if OVS is compiled without this feature and we explicitly
> configure it? Same for the reverse what if the kernel
On Tue, Sep 10, 2019 at 9:06 AM Gregory Rose wrote:
>
>
> On 9/10/2019 7:02 AM, Thomas Goirand wrote:
> > Hi Ben and others,
> >
> > I just want to know: does OVS 2.10 has support for IPv6 mac learning /
> > NDP, so that we can avoid the ipv6 broadcast storm in our cloud?
>
> OVS will switch/forwa
On 9/10/2019 7:02 AM, Thomas Goirand wrote:
Hi Ben and others,
I just want to know: does OVS 2.10 has support for IPv6 mac learning /
NDP, so that we can avoid the ipv6 broadcast storm in our cloud?
OVS will switch/forward IPv6 NDP traffic generated by network stations
with IPv6 enabled.
I
On 26 Aug 2019, at 16:33, David Marchand wrote:
> Add a coverage counter to help diagnose contention on the vhost txqs.
> This is seen as dropped packets on the physical ports for rates that
> are usually handled fine by OVS.
>
> Signed-off-by: David Marchand
LGTM, Acked-by: Eelco Chaudron
_
Hi William,
One comment below, but I’m also wondering if we should warn/log a
message if OVS is compiled without this feature and we explicitly
configure it? Same for the reverse what if the kernel does not support
this option, will it fail?
//Eelco
On 5 Sep 2019, at 22:51, William Tu wro
Hi Ben and others,
I just want to know: does OVS 2.10 has support for IPv6 mac learning /
NDP, so that we can avoid the ipv6 broadcast storm in our cloud?
Cheers,
Thomas Goirand (zigo)
P.S: I'm not registered to this list, please CC me.
___
dev mailin
On 10.09.2019 15:12, Eelco Chaudron wrote:
> Currently, OVS does not register and therefore not handle the
> interface reset event from the DPDK framework. This would cause a
> problem in cases where a VF is used as an interface, and its
> configuration changes.
>
> As an example in the following
On 08.09.2019 19:01, Sriram Vatala wrote:
> OVS may be unable to transmit packets for multiple reasons and
> today there is a single counter to track packets dropped due to
> any of those reasons. The most common reason is that a VM is
> unable to read packets fast enough causing the vhostuser port
Bleep bloop. Greetings Eelco Chaudron, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: Line is 80 characters long (recommended limit is 79)
#66 FILE: lib/netdev-dpdk.c:175
On 10.09.2019 13:43, Konieczny, TomaszX wrote:
> -Original Message-
> From: Ilya Maximets
> Sent: 10 September 2019 11:44
> To: Konieczny, TomaszX ; d...@openvswitch.org
> Cc: Stokes, Ian
> Subject: Re: [ovs-dev] [PATCH v1] netdev-dpdk: Fix flow control configuration.
>
> On 10.09.2019
Hi All,
I have addressed the comments given in patch v7. Please review the patch v8
and let me know your comments if any.
Thanks & Regards,
Sriram.
-Original Message-
From: Sriram Vatala
Sent: 08 September 2019 21:32
To: ovs-dev@openvswitch.org; i.maxim...@samsung.com
Cc: ktray...@redha
Currently, OVS does not register and therefore not handle the
interface reset event from the DPDK framework. This would cause a
problem in cases where a VF is used as an interface, and its
configuration changes.
As an example in the following scenario the MAC change is not
detected/acted upon unti
On 10.09.2019 14:11, Eelco Chaudron wrote:
>
>
> On 5 Sep 2019, at 14:40, Ilya Maximets wrote:
>
>> Hi Eelco,
>
>
>>> , 2 deletions(-)
>>>
>>> diff --git a/lib/netdev-dpdk.c b/lib/netdev-dpdk.c
>>> index bc20d6843..a23150387 100644
>>> --- a/lib/netdev-dpdk.c
>>> +++ b/lib/netdev-dpdk.c
>>> @@
On 5 Sep 2019, at 14:40, Ilya Maximets wrote:
Hi Eelco,
, 2 deletions(-)
diff --git a/lib/netdev-dpdk.c b/lib/netdev-dpdk.c
index bc20d6843..a23150387 100644
--- a/lib/netdev-dpdk.c
+++ b/lib/netdev-dpdk.c
@@ -362,6 +362,7 @@ struct netdev_dpdk {
bool attached;
/* If tr
-Original Message-
From: Ilya Maximets
Sent: 10 September 2019 11:44
To: Konieczny, TomaszX ; d...@openvswitch.org
Cc: Stokes, Ian
Subject: Re: [ovs-dev] [PATCH v1] netdev-dpdk: Fix flow control configuration.
On 10.09.2019 12:29, Ilya Maximets wrote:
> On 09.09.2019 14:39, Tomasz Konie
Bleep bloop. Greetings Vishal Deep Ajmera via dev, I am a robot and I have
tried out your patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: Line is 81 characters long (recommended limit is 79)
#218 FILE: lib/dpif
Problem:
In OVS-DPDK, flows with output over a bond interface of type “balance-tcp”
(using a hash on TCP/UDP 5-tuple) get translated by the ofproto layer into
"HASH" and "RECIRC" datapath actions. After recirculation, the packet is
forwarded to the bond member port based on 8-bits of the d
v5->v6:
Addressed comments from Ilya Maximets.
https://mail.openvswitch.org/pipermail/ovs-dev/2019-August/362001.html
Rebased to OVS master.
v4->v5:
Support for stats per hash bucket.
Support for dynamic load balancing.
Rebased to OVS Master.
v3->v4:
Addressed Ilya Maximets comments.
http
On 10.09.2019 12:29, Ilya Maximets wrote:
> On 09.09.2019 14:39, Tomasz Konieczny wrote:
>> Currently OVS is unable to change flow control configuration in DPDK
>> because new settings are being overwritten by current settings
>> with rte_eth_dev_flow_ctrl_get(). The fix restores correct order
>> o
From: Numan Siddique
The commit [1] removed OVN, but had to leave out some OVN bits
for the ovsdb-server raft testing. But "make install" is installing
ovn-nb/ovn-sb man entries and OVN schema files.
This patch excludes these.
"make install" is also installing ovn-nbctl/ovn-sbctl and this still
On 09.09.2019 14:39, Tomasz Konieczny wrote:
> Currently OVS is unable to change flow control configuration in DPDK
> because new settings are being overwritten by current settings
> with rte_eth_dev_flow_ctrl_get(). The fix restores correct order
> of operations and at the same time does not trigg
POSLEDNÍ VAROVÁNÍ d...@openvswitch.org!
Máte konečnou příležitost zachránit svůj
společenský život - já si srandu !!
Dávám vám posledních 72 hodin, abych provedl platbu,
než pošlu vίdeo s vaší ʍasturbací všem svým
přátelům a spolupracovníkům.
Naposledy jste navštívili Ƿornografickou stránku s
m
Здравствуйте!
Перейдем сразу к сути, чтобы не занимать Ваше время.
Доставим Ваш товар из Китая в максимально сжатые сроки.
По необходимости, поможем с закупкой, проверим качество товара перед отправкой,
проконтролируем безопасность доставки.
Заинтересовало?
Напишите нам!
Email: stiloszavi1...@mail
> Hi All,
>
> I am working on Virtio Crypto and could run DPDK virtio crypto use cases on
> both x86 and ARM.
>
> Now , I am trying to integrate virtio crypto with ovs-dpdk , is there any
> work done in this direction . Could someone please help with inputs.
Hi Harish,
Why do you want to inte
Redundant line continuation was missed while removing OVN
that broke distdir target and subsequently all the dependent
targets, e.g. distcheck:
make[1]:
*** No rule to make target 'nodist_ovn_lib_libovn_la_SOURCES',
needed by 'distdir'. Stop.
CC: Mark Michelson
Fixes: f3e24610ea18 ("R
Bleep bloop. Greetings Numan Siddique, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: Line lacks whitespace around operator
WARNING: Line lacks whitespace around operator
On Mon, Sep 9, 2019 at 1:58 AM Ankur Sharma
wrote:
> During E-W routing for vlan backed networks, we replace router port
> mac with chassis mac, when packet leaves the source hypervisor.
>
> As a result, the destination VM (on remote hypervisor) will see
> chassis mac as source mac in received pa
On Wed, Sep 4, 2019 at 11:21 PM Mark Michelson wrote:
> On 9/2/19 1:09 PM, nusid...@redhat.com wrote:
> > From: Numan Siddique
> >
> > Now that OVN has it's own rundir, "ovs-appctl -t
> ovn-controller/ovn-northd"
> > doesn't work. To fix this, ovn-appctl utility is added which
> > looks for the
From: Numan Siddique
This was missing when OVN was split from OVS.
Signed-off-by: Numan Siddique
---
Makefile.am | 17 +
TODO_SPLIT.rst | 6 ---
automake.mk | 84 +
ovn-nb.xml | 2 +-
rhel/ovn-fedor
From: Numan Siddique
Now that OVN has it's own rundir, "ovs-appctl -t ovn-controller/ovn-northd"
doesn't work. To fix this, ovn-appctl utility is added which
looks for the OVN pid/ctl files in the ovn rundir.
The code is taken from ovs-appctl.c and modified to use ovn_rundir()
instead of ovs_run
Hi Mark,
Few comments below.
On Sat, Sep 7, 2019 at 2:38 AM Mark Michelson wrote:
> This document serves to provide an explanation for how OVN will remain
> compatible with OVS. It provides instructions for OVN contributors for
> how to maintain compatibility even across older versions of OVS
39 matches
Mail list logo
