Hi Team,
I am planning to start implementing the Shaping support in ovs-dpdk.
Please let me know if anyone has already started/ has any road map for shaping
implementation in ovs-dpdk.
Regards,
Gayathri
The information contained in this electronic message and any attachments to
this message
Test Case:
Port bond12
Interface "eth1"
Interface "eth2"
1. generate random packets, and send them out of bond12 ==> load balance on
eth1 and eth2.
2. ip link set eth1 down ==> all packets go to eth2 (ovs-appctl bond/show)
3. ip link set eth1 up==> after quite a long time, still no
BFD won't really be useful until there's a story
> around fail-over, which I expect before too long, but isn't fully formed yet.
>
I have been trying to figure out if I can access BFD states from outside
applications. I see that the table records get updated, but how best to signal
that to an
> On Feb 29, 2016, at 11:28 AM, Shalit, Amir wrote:
>
> I’m working on a hw-vtep support in openswitch. Initial release doesn’t have
> ACL support nor BFD.
> How prevalent is ACL in OVN setups (deployments) ?
> How prevalent is BFD ?
We don't have a list of who is using
I'm working on a hw-vtep support in openswitch. Initial release doesn't have
ACL support nor BFD.
How prevalent is ACL in OVN setups (deployments) ?
How prevalent is BFD ?
Thanks,
Amir Shalit
___
discuss mailing list
discuss@openvswitch.org
"discuss" wrote on 02/29/2016 08:37:02
AM:
> From: Ryan Moats/Omaha/IBM@IBMUS
> To: discuss@openvswitch.org
> Date: 02/29/2016 08:37 AM
> Subject: [ovs-discuss] OVSDB change tracking - is the delete case
> really usable?
> Sent by: "discuss"
All-
I bumped into the following while trying to persist the logical flow
information in ovn-controller:
When OVSDB change tracking is turned on, sequence numbers
are generated for each row delete event. However, the memory
the row uses is freed anyway, so code that is looping through
tracked
Hi all,
When I test the ovs-dpdk, I get a segfault of ovs-vswitch,and the ovs-vswitch
crashed
The message log :
9 10:20:33 A06-R12-302F0111-I32-13 kernel: pmd38[1598]: segfault at 8 ip
005d1fc7 sp 7f8f59bf1900 error 4 in ovs-vswitchd[40+36a000]
And the simple analysis of the