Hi all,
Currently OVS2.12 has support datapath clone feature as a default
selection. When broadcast a packet to each vxlan tunnel port, each
tnl_push/output action using OVS_ACTION_ATTR_CLONE nested in actions.
As a result, each tnl_push/output action use more bytes(about eight
bytes) than old OVS2.7 versions. That means a same length action memory will
support less number of output ports.
Since there is a limit length(65535) of actions memory bytes used for
ofproto switch putting flows to the datapath, after we upgrade to OVS2.12,
some vxlan tunnel port can't receive the broadcast packet and the traffic may
be abnormal. And in OVS2.7 that ports can work successfully.
For this question, I have two advices:
1) Enlarge the limit length(65535) of actions memory bytes to support
more vxlan tunnel port.
a) For kernel datapath, there may be more complicated implement
because the limit length of netlink attributes and messages. Can we add a
special ATTR type for extra oversized actions?
2) Disable the datapath clone feature in my cases which has too much
vxlan tunnel ports.
a) The userspace datapath doesn't work after disable the feature,
maybe some codes related clone feature such as native vxlan xlate also works.
More effort is needed to figure out the reason.
Is there any comments or opinions?
Look forward to your reply, thanks.
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
