This article needs additional citations for verification. (March 2010) (Learn how and when to remove this template message)
In computer networking, jumbo frames or jumbos are Ethernet frames with more than 1500 bytes of payload, the limit set by the IEEE 802.3 standard. Conventionally, jumbo frames can carry up to 9000 bytes of payload, but variations exist and some care must be taken using the term. Many Gigabit Ethernet switches and Gigabit Ethernet network interface cards can support jumbo frames. Some Fast Ethernet switches and Fast Ethernet network interface cards can also support jumbo frames. Most national research and education networks (such as Internet2, National LambdaRail, ESnet, GÉANT and AARNet) support jumbo frames, but most commercial Internet service providers do not.
Each Ethernet frame must be processed as it passes through the network. Processing the contents of a single large frame is preferable to processing the same content broken up into smaller frames, as this makes better use of available CPU time by reducing interrupts. This also minimizes the overhead byte count and reduces the number of frames needing to be processed. This is analogous to physically mailing a packet of papers instead of several single envelopes with one sheet each, saving envelopes and cutting sorting time.
Jumbo frames gained initial prominence when Alteon WebSystems introduced them in their ACEnic Gigabit Ethernet adapters. Many other vendors also adopted the size; however, jumbo frames did not become part of the official IEEE 802.3 Ethernet standard.
Jumbo frames or 9000-byte payload frames have the potential to reduce overheads and CPU cycles. Recent work has also demonstrated the positive effect that jumbo frames have on end-to-end TCP performance. The presence of jumbo frames may have an adverse effect on network latency, especially on low bandwidth links. The frame size used by an end-to-end connection is typically limited by the lowest frame size in intermediate links. 802.5 Token Ring can use frames with a 4464-byte MTU, FDDI can transport 4352 byte, ATM 9180 byte and 802.11 can transport 7935 byte MTUs. The IEEE 802.3 Ethernet standard only mandates support for 1500-byte MTU frames, 1518 byte total frame size (1522 byte with the optional IEEE 802.1Q VLAN/QoS tag).
The use of 9000 bytes as preferred payload size for jumbo frames arose from discussions within the Joint Engineering Team of Internet2 and the U.S. federal government networks. Their recommendation has been adopted by all other national research and education networks. In order to meet this mandatory purchasing criterion, manufacturers have in turn adopted 9000 bytes as the conventional MTU size, with a jumbo frame size of at least 9018/9022 bytes (without and with IEEE 802.1Q field). Most Ethernet equipment can support jumbo frames up to 9216 bytes.
IEEE 802.1AB-2009 and IEEE 802.3bc-2009 added LLDP discovery to standard Ethernet for maximum frame length (TLV subtype 4). It allows frame length detection on a port by a two-octet field. As of IEEE 802.3-2015, allowed values are 1518 (only basic frames), 1522 (802.1Q-tagged frames), and 2000 (multi-tagged, envelope frames).
Larger frames are more likely to suffer undetected errors with the simple CRC32 error detection used in Ethernet frames — a larger amount of data increases the probability that several errors cancel each other out. Consequently, additional mechanisms have been developed to improve error detection on higher network layers.
IETF solutions for adopting jumbo frames avoids data integrity reduction of the service data unit through use of the Castagnoli CRC polynomial being implemented within the SCTP transport (RFC 4960) and iSCSI (RFC 7143). Selection of this polynomial was based upon work documented in the paper "32-Bit Cyclic Redundancy Codes for Internet Applications". The Castagnoli polynomial 0x1EDC6F41 achieves the Hamming distance HD=6 beyond one Ethernet MTU (to a 16,360 bit data word length) and HD=4 to 114,663 bits, which is more than 9 times the length of an Ethernet MTU. This gives two additional bits of error detection ability at MTU-sized data words compared to the Ethernet CRC standard polynomial while not sacrificing HD=4 capability for data word sizes up to and beyond 72 kbits.
By using a CRC checksum rather than simple additive checksums as contained within the UDP and TCP transports, errors generated internal to NICs can be detected as well. Both TCP and UDP have proven ineffective at detecting bus specific bit errors, since these errors with simple summations tend to be self-cancelling. Testing that led to adoption of RFC 3309 compiled evidence based upon simulated error injection against real data that demonstrated as much as 2% of these errors were not being detected.
One of the major impediments toward the adoption of jumbo frames has been the inability to upgrade existing Ethernet infrastructure that would be needed to avoid a reduction in the ability to detect errors. CRC calculations done in software have always resulted in slower performance than that achieved when using simple additive checksums, as found with TCP and UDP. To overcome this performance penalty, NICs that off-load SCTP checksum calculations are available, and CPUs that support SSE4.2 can utilize the CRC32c instruction featured in the extension's vector math instruction set.
Support of Castagnoli CRC polynomial within a general purpose transport designed to handle data chunks, and within a TCP transport designed to carry SCSI data, both provide improved error detection rates despite the use of jumbo frames where increase of the Ethernet MTU would have otherwise resulted in a significant reduction in error detection.
Some vendors include the headers in the size settings while others do not, that is either the maximum frame size (including frame headers, maximum layer 2 packet size) or the maximum transfer unit (MTU) (maximum layer 3 packet size excluding frame headers). Therefore, you might find that different values must be configured in equipment from different vendors to make the settings match. A mixture of devices configured for jumbo frames and devices not configured for jumbo frames on a network has the potential to cause network performance issues.
Jumbo frames can raise the efficiency of Ethernet and network processing in hosts by reducing the overhead, as seen in the following example with TCP over IPv4. The processing efficiency of the hosts can increase by the ratio of the payloads (approximately 6 times improvement in this example). Whether this is significant depends on how packets are processed in the host. Hosts that use a TCP offload engine will receive less benefit than hosts that process frames with their CPU.
|Frame type||MTU||Layer 1 overhead||Layer 2 overhead||Layer 3 overhead||Layer 4 overhead||Payload size||Total transmitted[a]||Efficiency[b]|
|1460 byte||1538 byte||94.93%|
|8960 byte||9038 byte||99.14%|
|Other frame sizes for reference|
|IEEE 802.11||7935||PLCP preamble & header
|frame header & security ovhd
|7895 byte||8015 + IPG size byte||< 98.5%|
- Total transmitted size is the sum of the payload size and all overhead sizes.
- Efficiency is calculated by dividing the payload size by the total transmitted size.
Baby giant frames
Baby giant or baby jumbo frames are Ethernet frames that are only slightly larger than allowed by the IEEE Ethernet standards. Baby giant frames are for example required to enable IP/MPLS over Ethernet to deliver Ethernet services. Most implementations will require non-jumbo user frames to be encapsulated into MPLS frame format which in turn may be encapsulated into a proper Ethernet frame format with EtherType values of 0x8847 and 0x8848. The increased overhead of extra MPLS and Ethernet headers means that the support of 1600 byte frames is a mandatory requirement in Carrier Ethernet networks.
Super jumbo frames
Super jumbo frames (SJFs) are generally considered to be frames that have a payload size of over 9000 bytes. The relative scalability of network data throughput as a function of packet transfer rates is related in a complex manner  to payload size per packet. Generally, as line bit rate increases, the packet payload size should increase in direct proportion to maintain equivalent timing parameters. This however implies the covariant scaling of numerous intermediating logic circuits along the network path to accommodate the maximum frame size required. As it has been a relatively difficult, and somewhat lengthy, process to increase the path MTU of high performance national research and education networks from 1500 bytes to 9000 bytes or so, a subsequent increase, possibly to 64000 bytes for example, may take some time.
The main factor involved with an increase in the maximum segment size (MSS) is an increase in the available memory buffer size in all of the intervening persistence mechanisms along the path. The main benefit of this is the reduction of the packet rate, both at end nodes and intermediate transit nodes. As the nodes in general use reciprocating logic to handle the packets, the total number of machine cycles spent processing packet headers decreases as the average MSS of the packets increases given a certain total amount of data transmitted. This relationship becomes increasingly important as average network line bit rate increases to 10 gigabits per second, and above.
By making CPU load independent of frame size, large send offload (LSO) is an approach to eliminate the per-packet overhead that jumbo frames were designed to reduce. Large receive offload (LRO), the inbound counterpart of large segment offload, does not quite eliminate per-packet overhead borne by the CPU, therefore jumbo frames remain beneficial for inbound traffic. Jumbo frames are also still useful from a bandwidth perspective as they reduce the amount of bandwidth used for non-data overhead.
- Jumbogram – large packets for IPv6
- "Ethernet Jumbo Frames". Ethernet Alliance. 2009-11-12. Retrieved 2015-06-18.
- "Jumbo/Giant Frame Support on Catalyst Switches Configuration Example". Cisco. Retrieved 2011-08-22.
Catalyst 3750/3560 Series switches support an MTU of 1998 bytes for all 10/100 interfaces
- "Ethernet Jumbo Frames" (PDF). EthernetAlliance.org. Retrieved April 28, 2017.
- Jeff Caruso (October 22, 1998). "Alteon still stumping for Jumbo Frames". Network World. Archived from the original on 2012-10-15. Retrieved July 4, 2011.
- Foong, A; T. Huff; H. Hum; J. Patwardhan; G. Regnier (2003). "TCP Performance Re-visited". In IEEE International Symposium on Performance of Systems and Software.
- D Murray; T Koziniec; K Lee; M Dixon (2012). "Large MTUs and internet performance". 13th IEEE Conference on High Performance Switching and Routing (HPSR 2012).
- Rick Summerhill (17 Feb 2003), rrsum-almes-mtu, Internet2
- Scott Hogg (2013-03-06), Jumbo Frames, Network World, retrieved 2013-08-05,
Most network devices support a jumbo frame size of 9216 bytes.
- IEEE 802.3 79.3.4 Maximum Frame Size TLV
- IEEE 802.3 3.2.7 MAC Client Data field
- "32-Bit Cyclic Redundancy Codes for Internet Applications" by Philip Koopman, ECE Department & ICES, Carnegie Mellon University
- "What is the Jumbo Frame Supported by Switches and Adapters?". Netgear. Retrieved 2013-08-05.
- Philip (October 20, 2016). "Wireless Network Speed Tweaks". speedguide.net. Retrieved October 20, 2016.
- IEEE 802.11-2012 8.2.3 General frame format
- RFC-3032, MPLS Label Stack Encoding
- Ceragon, Jumbo Frames: The Microwave Perspective, Technical brief Archived 2012-09-15 at the Wayback Machine.
- 16 000–64 000 B pMTU experiments with simulation: The case for super jumbo frames at Supercomputing ’05
- "Coding Relic: Requiem for Jumbo Frames". 2011-12-07. Retrieved 2011-12-07.
- Jumbo Frames – Where to use it?
- Jumbo frames? Yes!, by Selina Lo, Alteon Networks, 2/23/1998 in NetworkWorld
- SJF Supercomputing 2005 Demo
- Pushing up the Internet MTU
- IEEE 802.3as Frame Expansion Task Force
- 32-Bit Cyclic Redundancy Codes for Internet Applications
- Need To Know: Jumbo Frames in Small Networks
- How to Jumbo Frames in Archlinux