Hi,
to avoid missing another work already been done (and google didn't find me
anything).
Is there already work going on to get --user and dpdk working together?
(see http://openvswitch.org/pipermail/dev/2015-September/060382.html)
Background:
While setting up a vhost_user based ovs-dpdk setup I'm
Il 2016-01-26 01:13, Shivram Krishnan ha scritto:
Hey Guys,
Hope you all are doing well.
I have a simple three switches set up. Lets call them A,B and C . A is
connected to B and C , B is connected to A and C and C is connected to A
and B.
A,B,C are running quagga as a routing daemon and are a
Daniele, I think that you said in our meeting today that there was some
sort of bug that falsely blames a thread. Can you explain further?
On Mon, Jan 25, 2016 at 09:29:52PM +0100, Patrik Andersson R wrote:
> Right, that is likely for sure. Will look there first.
>
> What do you think of the cas
Hi,
I'd like to know is there any patch that supports for 802.1qad (QinQ).
Or is there any limitation to support QinQ in ovs2.4.0?
Best Regards
tutumei
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
Hey Guys,
Hope you all are doing well.
I have a simple three switches set up. Lets call them A,B and C . A is
connected to B and C , B is connected to A and C and C is connected to A
and B.
A,B,C are running quagga as a routing daemon and are able to exchange the
routing information.
Now I inst
Right, that is likely for sure. Will look there first.
What do you think of the case where the thread is "main". I've got
examples of
this one as well. Have not been able to figure out so far what would
cause this.
...
ovs-vswitchd.log.1.1.1.1:2016-01-23T01:47:19.026Z|00016|ovs_rcu(urcu2)|WAR
Also I know the split weight is an integer. I have three out ports. If I
set split weight to 1, 1 and 1 or I set split weight to 2, 2 and 2, what is
the difference ? It is the same, right ? The group will normalize them
automatically ?
On Mon, Jan 25, 2016 at 1:39 PM, Ben Pfaff wrote:
> On Mon,
On Mon, Jan 25, 2016 at 03:09:09PM +0100, Patrik Andersson R wrote:
> during robustness testing, where VM:s are booted and deleted using nova
> boot/delete in rather rapid succession, VMs get stuck in spawning state
> after
> a few test cycles. Presumably this is due to the OVS not responding to po
On Mon, Jan 25, 2016 at 12:05:03PM -0500, Jiaqi Zheng wrote:
> I only have three flow and the group table with three outport is configured
> with the same split weight :
> Flow 1: source mac: 10.0.0.1 destination mac: 10.0.0.2
> Flow 2: source mac: 10.0.0.1 destination mac: 10.0.0.3
> Flow 3: so
I only have three flow and the group table with three outport is configured
with the same split weight :
Flow 1: source mac: 10.0.0.1 destination mac: 10.0.0.2
Flow 2: source mac: 10.0.0.1 destination mac: 10.0.0.3
Flow 3: source mac: 10.0.0.1 destination mac: 10.0.0.4
You mean the packets will
On Sat, Jan 23, 2016 at 06:25:35PM -0800, Jiaqi Zheng wrote:
> In my experiments, it seems like something wrong.
>
> In my experiments, H1 is the source, another three hosts H2, H3 and H4 are
> destination. The source host H1 send packets to other three hosts at the
> same time. I set group table
On Mon, Jan 25, 2016 at 10:24:38AM -0500, Jiaqi Zheng wrote:
> My ovs version is 2.3.0.
>
> I know if the group table is configured with different split weight. The
> flow is splitted through different outport according to configured split
> weight.
>
> In my experiments, it seems like the split
On Sat, Jan 23, 2016 at 3:59 AM, zhangqunjian wrote:
>
> Hi, I use OVS created vxlan tunnel based on IPv6. As far as I know, GitHub
> master branch has been commited part code of this function. when I used it
> into my project,I found that vxlan over IPv6 configuration is working
> properly,but f
Hi All,
My ovs version is 2.3.0.
I know if the group table is configured with different split weight. The
flow is splitted through different outport according to configured split
weight.
In my experiments, it seems like the split is flow-based, rather than
packet-based. right ?
Also could I kno
Hi,
during robustness testing, where VM:s are booted and deleted using nova
boot/delete in rather rapid succession, VMs get stuck in spawning state
after
a few test cycles. Presumably this is due to the OVS not responding to port
additions and deletions anymore, or rather that responses to thes
15 matches
Mail list logo