On 3/18/2018 1:45 AM, Chas Williams wrote:
> From: Chas Williams <ch...@att.com>
>
> The vmxnet3 never attempts link speed negotiation. As a virtual device
> the link speed is vague at best. However, it is important for certain
> applications, like bonding, to see a consistent link_status. 802.3ad
> requires that only links of the same cost (link speed) be enslaved.
> Keeping the link status consistent in vmxnet3 avoids races with bonding
> enslavement.
>
> Author: Thomas Monjalon <tho...@monjalon.net>
> Date: Fri Jan 5 18:38:55 2018 +0100
>
> Fixes: 1e3a958f40b3 ("ethdev: fix link autonegotiation value")
> Cc: sta...@dpdk.org
>
> Signed-off-by: Chas Williams <ch...@att.com>
>From Thomas Monjalon <tho...@monjalon.net>:
> Yes, OK for ETH_LINK_FIXED.
>From Yong Wang <yongw...@vmware.com>:
> Yes and it makes sense for vmxnet3 to use ETH_LINK_FIXED.
Converted into explicit ack:
Acked-by: Yong Wang <yongw...@vmware.com>
Applied to dpdk-next-net/master, thanks.
