Hi Team,
We are doing comparison of throughput and CPU consumption between OVS 2.3.0
and kernel bridge with different packet size.
We are observing huge difference in performance. With frame size 64 and 128
bytes unidirectional traffic from port1 to port2 below are the numbers.
*OVS 2.3.0 (Dual
hi,
This a patch for performance optimization when adding lots of ports.
The patch is based on version 2.3.0, and I have run all the testsuites.
The main optimize points are :
1) monitor some special records instead of monitor all the records
2) remove column "ports" in table "Bridge", r
On Thu, Dec 04, 2014 at 04:22:47PM +0100, Daniel Spiekermann wrote:
> thx for your answer. Could you please tell me which source file
> contains relevant parts for accessing the ovsdb. Maybe I can extract
> the information directly.
Kernel flows are not in OVSDB.
__
Thanks a lot guys it worked.[?]
On Wed, Dec 3, 2014 at 6:09 PM, Flavio Leitner wrote:
> On Wed, Dec 03, 2014 at 03:16:34PM +0530, Aman Kumar wrote:
> > > It supports only IGMPv1 and IGMPv2, so make sure the membership
> > reports are using either one of those versions.
> >
> > The multicast
Hi,
we noticed, that OvS stopped to learning some MAC addresses. In our
setup, on one physical machine (Debian 7 + OvS 2.0.1) we have multiple
virtual machines, using Xen as hypervisor.
Currently if we start some tests on one of virtual machines, it
broadcast this traffic to all other virtual
If I understand the bug report correctly, you are actually proposing
to enhance the ovs-docker script to also support setting the default
gateway. Am I Correct? If so, would you mind sending a patch to
d...@openvswitch.org using 'git format-patch' and 'git send-email'? If
you prefer that I do it in
Mani, since this seems to be less of an OVS discussion and more of a libvirt
discussion, I'll respond directly to you with more detail regarding your
question in a subsequent e-mail. If others on the list are interested in the
same information, please let me know.
On Dec 3, 2014, at 12:29 PM,
Hi Ben,
thx for your answer. Could you please tell me which source file contains
relevant parts for accessing the ovsdb. Maybe I can extract the information
directly.
Thx
Daniel
> Am 04.12.2014 um 02:42 schrieb Ben Pfaff :
>
> Thanks for the input.
>
> We've had a couple of requests for a
Hello,
I have a requirement to learn the IP address of VM's, given its MAC
address/Vlan tag when OVS is the virtual switch deployed. This is a very
generic requirement since the VM's IP address can either be launched through
Orchestrator like Openstack/vCenter or external DHCP agents or even ass
On Thu, Dec 04, 2014 at 03:25:08PM +0530, Aman Kumar wrote:
> Thanks a lot guys it worked.[?]
Glad to hear that!
fbl
>
> On Wed, Dec 3, 2014 at 6:09 PM, Flavio Leitner wrote:
>
> > On Wed, Dec 03, 2014 at 03:16:34PM +0530, Aman Kumar wrote:
> > > > It supports only IGMPv1 and IGMPv2, so m
I posted a patch that should resolve this, any chance you could try it out?
Here: http://openvswitch.org/pipermail/dev/2014-December/049420.html
Thanks,
Jarno
Hi Jarno,
I've applied the patch, and the test does pass now.
testlog:
---
[root@ppc64 ovs-test]# make check TESTSUITEFLAGS='-
11 matches
Mail list logo
