> In the scenario of XL710, the link speed which stored in the table of > Interface is not 40G. Because the implementation of query of link speed > only support to 10G, the parameter 'current' will be a random value in the > scenario of higher link speed. In this case, incorrect link speed of XL710 > nic will be stored in the database. >
Good catch, I've tested and it works as expected. I'll add this to the dpdk_merge pull request for this week and backport it to the previous release branches also. Thanks Ian > Signed-off-by: Xu Binbin <[email protected]> > --- > lib/netdev-dpdk.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/lib/netdev-dpdk.c b/lib/netdev-dpdk.c index ac02a09..e4b6ced > 100644 > --- a/lib/netdev-dpdk.c > +++ b/lib/netdev-dpdk.c > @@ -2735,6 +2735,9 @@ netdev_dpdk_get_features(const struct netdev > *netdev, > if (link.link_speed == ETH_SPEED_NUM_10G) { > *current = NETDEV_F_10GB_FD; > } > + if (link.link_speed == ETH_SPEED_NUM_40G) { > + *current = NETDEV_F_40GB_FD; > + } > } > > if (link.link_autoneg) { > -- > 1.8.3.1 > > _______________________________________________ > dev mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-dev _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
