I am afraid my observation for openvswitch 2.6.0 is wrong, for 3.10.45,
USE_UPSTREAM_TUNNEL is also not defined, and after confirm with my
colleague, openvswitch 2.5.0 + 3.10.45 also face the same poor bandwidth
issue.
So the problem applies for both openvswitch 2.5.0 and 2.6.0 on 3.10.45, is
Hi List,
We have now testing openvswitch 2.6.0 on kernel 3.10.45, however we noticed
there is performance drop than openvswitch 2.5.0 on the same kernel, which
iperf can only have a 2G bandwidth for a pair of 10G links.
After check the code, it seems on openvswitch 2.5.0, HAVE_METADATA_DST
macro
Hi everyone,
I've been running into some problems with the balancing of traffic using
the group type select and I'm wondering if it's something I'm doing wrong
or a potential issue in ovs.
So the setup is quite simple, I'm using mininet to setup a fat-tree
topology with a k of 4, so I end-up
Thank you guys,
it would be nice to have capability bit for bundles, I think it's defined in
1.4.1 and later.
Anyway, I have another question. Is there any coverage map of OpenFlow spec
(versions 1.3, 1.4, 1.5 ...) implementation in OVS.
It's not so easy to create bigger picture from release
Thanks Stringer. The problem was built-in module loaded every time instead
of the newly installed.
Now I've another issue. As i'm trying to get the CPU time, but it seems
time.h doesn't work. I tried clock(), clock_gettime() but both of them
don't work is there any other way to find the cpu time?
Hello all,
I am looking for implementation details of the Tuple Space Search algorithm in
the MegaFlow Cache. More specifically, I am interested in how ranges are
handled by the tuple space search lookup algorithm. Is each range converted
into (a) prefix(es) ? Are ranges converted into Nesting
