The short answer is that MTU is not an application parameter but a system configuration parameter. As such it is the domain of the control/management plane rather than the data plane. The data plane simply uses the MTU that has been configured elsewhere. Applications use higher-level segmenting like the TCP MSS that is negotiated for each connection.
As a practical matter, at 10Gb and above link speeds (what ODP is designed for), all interfaces should be running with 9K jumbo frames anyway. MTU is something of a legacy from the early days of networking where primitive low-speed devices had extremely limited buffering capacities, necessitating these tiny MTU values. They are really not relevant to 21st-century data plane processing. On Thu, Jan 28, 2016 at 9:06 AM, Mike Holmes <[email protected]> wrote: > > commit 45598fea1a8a64ab49e191224784188382fbd466 > Author: Petri Savolainen <[email protected]> > Date: Thu Jan 21 11:39:29 2016 +0200 > > api: pktio: remove odp_pktio_set_mtu > > Not all hardware can change MTU size from ODP application. > > Reviewed-by: Petri Savolainen <[email protected]> > Signed-off-by: Maxim Uvarov <[email protected]> > > > On 28 January 2016 at 08:30, Zoltan Kiss <[email protected]> wrote: > >> Hi, >> >> Is there a specific reason why we don't have an MTU setting API, but only >> one to query it? >> >> Zoli >> _______________________________________________ >> lng-odp mailing list >> [email protected] >> https://lists.linaro.org/mailman/listinfo/lng-odp >> > > > > -- > Mike Holmes > Technical Manager - Linaro Networking Group > Linaro.org <http://www.linaro.org/> *│ *Open source software for ARM SoCs > "Work should be fun and collborative, the rest follows" > > > > _______________________________________________ > lng-odp mailing list > [email protected] > https://lists.linaro.org/mailman/listinfo/lng-odp > >
_______________________________________________ lng-odp mailing list [email protected] https://lists.linaro.org/mailman/listinfo/lng-odp
