> From: Eli Cohen <elic@xxxxxxxxxx> > Sent: Wednesday, November 24, 2021 10:40 PM > > Make sure to offer VIRTIO_NET_F_MTU since we configure the MTU based on > what was queried from the device. > > This allows the virtio driver to allocate large enough buffers based on the > reported MTU. > > Signed-off-by: Eli Cohen <elic@xxxxxxxxxx> > --- > drivers/vdpa/mlx5/net/mlx5_vnet.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/vdpa/mlx5/net/mlx5_vnet.c > b/drivers/vdpa/mlx5/net/mlx5_vnet.c > index 465e832f2ad1..ed7a63e48335 100644 > --- a/drivers/vdpa/mlx5/net/mlx5_vnet.c > +++ b/drivers/vdpa/mlx5/net/mlx5_vnet.c > @@ -1956,6 +1956,7 @@ static u64 mlx5_vdpa_get_features(struct > vdpa_device *vdev) > ndev->mvdev.mlx_features |= > BIT_ULL(VIRTIO_NET_F_CTRL_MAC_ADDR); > ndev->mvdev.mlx_features |= BIT_ULL(VIRTIO_NET_F_MQ); > ndev->mvdev.mlx_features |= BIT_ULL(VIRTIO_NET_F_STATUS); > + ndev->mvdev.mlx_features |= BIT_ULL(VIRTIO_NET_F_MTU); It is better to set this feature bit along with the writing the RO config.mtu area, adjacent to query_mtu() call. _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
