From 70fc25ad6e71a99b5802eb92b95c26407acbe990 Mon Sep 17 00:00:00 2001 From: Michael Brown Date: Wed, 25 Jan 2017 14:48:24 +0000 Subject: [netdevice] Limit MTU by hardware maximum frame length Separate out the concept of "hardware maximum supported frame length" and "configured link MTU", and limit the latter according to the former. In networks where the DHCP-supplied link MTU is inconsistent with the hardware or driver capabilities (e.g. a network using jumbo frames), this will result in iPXE advertising a TCP MSS consistent with a size that can actually be received. Note that the term "MTU" is typically used to refer to the maximum length excluding the link-layer headers; we adopt this usage. Signed-off-by: Michael Brown --- src/include/ipxe/netdevice.h | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'src/include') diff --git a/src/include/ipxe/netdevice.h b/src/include/ipxe/netdevice.h index a1d207ffc..d498ab697 100644 --- a/src/include/ipxe/netdevice.h +++ b/src/include/ipxe/netdevice.h @@ -397,9 +397,16 @@ struct net_device { struct retry_timer link_block; /** Maximum packet length * - * This length includes any link-layer headers. + * This is the maximum packet length (including any link-layer + * headers) supported by the hardware. */ size_t max_pkt_len; + /** Maximum transmission unit length + * + * This is the maximum transmission unit length (excluding any + * link-layer headers) configured for the link. + */ + size_t mtu; /** TX packet queue */ struct list_head tx_queue; /** Deferred TX packet queue */ -- cgit v1.2.3-55-g7522