3143d86b69
Updates for patchset 2 review comments Changed link depth of main Planning index and added some narrative guidance Added planning/openstack as sibling of planning/kubernetes Related additions to abbrevs.txt Added max-workers substitution to accomodate StarlingX/vendor variants Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: Ibff9af74ab3f2c00958eff0e33c91465f1dab6b4 Signed-off-by: Stone <ronald.stone@windriver.com>
1.8 KiB
Executable File
Ethernet MTU
The of an Ethernet frame is a configurable attribute in . Changing its default size must be done in coordination with other network elements on the Ethernet link.
In the context of , the refers to the largest possible payload on the Ethernet frame on a particular network link. The payload is enclosed by the Ethernet header (14 bytes) and the CRC (4 bytes), resulting in an Ethernet frame that is 18 bytes longer than the size.
The original IEEE 802.3 specification defines a valid standard Ethernet frame size to be from 64 to 1518 bytes, accommodating payloads ranging in size from 46 to 1500 bytes. Ethernet frames with a payload larger than 1500 bytes are considered to be jumbo frames.
For a network, the frame also includes a 4-byte ID header, resulting in a frame size 22 bytes longer than the size.
In , you can configure the size for the following interfaces and networks:
- The management, cluster host and network interfaces on the controller. The size for these interfaces is set during initial installation.
- Additional interfaces configured for container workload connectivity to external networks,
In all cases, the default size is 1500. The minimum value is 576, and the maximum is 9216.