[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a38a9877-4b01-22b3-ac62-768265db0d5a@gmail.com>
Date: Sat, 18 Dec 2021 13:53:01 -0700
From: David Ahern <dsahern@...il.com>
To: Parav Pandit <parav@...dia.com>, stephen@...workplumber.org,
netdev@...r.kernel.org
Cc: virtualization@...ts.linux-foundation.org, mst@...hat.com,
jasowang@...hat.com
Subject: Re: [iproute2-next v2 4/4] vdpa: Enable user to set mtu of the vdpa
device
On 12/17/21 1:08 AM, Parav Pandit wrote:
> @@ -204,6 +217,8 @@ static void vdpa_opts_put(struct nlmsghdr *nlh, struct vdpa *vdpa)
> if (opts->present & VDPA_OPT_VDEV_MAC)
> mnl_attr_put(nlh, VDPA_ATTR_DEV_NET_CFG_MACADDR,
> sizeof(opts->mac), opts->mac);
> + if (opts->present & VDPA_OPT_VDEV_MTU)
> + mnl_attr_put_u16(nlh, VDPA_ATTR_DEV_NET_CFG_MTU, opts->mtu);
Why limit the MTU to a u16? Eric for example is working on "Big TCP"
where IPv6 can work with Jumbograms where mtu can be > 64k.
https://datatracker.ietf.org/doc/html/rfc2675
Powered by blists - more mailing lists