On Mon, Apr 28, 2014 at 11:53:51PM -0700, Alex Wang wrote:
> Based on the policy of 'OVS_VPORT_ATTR_UPCALL_PID', if upcall should
> not be sent to userspace (i.e. the number of handler threads is zero),
> the netlink message for creating vport should be an one-element array of
> value 0. However,
Based on the policy of 'OVS_VPORT_ATTR_UPCALL_PID', if upcall should
not be sent to userspace (i.e. the number of handler threads is zero),
the netlink message for creating vport should be an one-element array of
value 0. However, dpif_linux_port_add__() fails to obey it and generates
zero-payload
