Jumbo frame

Last updated

Ethernet frame illustrating variable-length payload. Jumbo frames have payloads greater than 1500 bytes. Ethernet frame.svg
Ethernet frame illustrating variable-length payload. Jumbo frames have payloads greater than 1500 bytes.

In computer networking, jumbo frames are Ethernet frames with more than 1500 bytes of payload, the limit set by the IEEE 802.3 standard. [1] The payload limit for jumbo frames is variable: while 9000 bytes is the most commonly used limit, smaller and larger limits exist. Many Gigabit Ethernet switches and Gigabit Ethernet network interface controllers and some Fast Ethernet switches and Fast Ethernet network interface cards can support jumbo frames. [2]

Contents

Inception

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. [3] 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 in 1998, when Alteon WebSystems introduced them in their ACEnic Gigabit Ethernet adapters. [4] Many other vendors also adopted the size; however, jumbo frames are not part of the official IEEE 802.3 Ethernet standard.

Adoption

Jumbo frames have the potential to reduce overheads and CPU cycles [5] and have a positive effect on end-to-end TCP performance. [6] 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 support 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 originally mandated support for 1500-byte MTU frames, 1518 byte total frame size (1522 byte with the optional IEEE 802.1Q VLAN/QoS tag). The IEEE 802.3as update grandfathered in multiple common headers, trailers, and encapsulations by creating the concept of an envelope where up to 482 bytes of header and trailer could be included, and the largest IEEE 802.3 supported Ethernet frame became 2000 bytes.

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. [7] Their recommendation has been adopted by all other national research and education networks.[ citation needed ] Manufacturers have in turn adopted 9000 bytes as the conventional MTU size, with a total jumbo frame size of between 9014 and 9022 bytes with Ethernet headers included. [8] Most Ethernet equipment can support jumbo frames up to 9216 bytes. [9]

IEEE 802.1AB-2009 and IEEE 802.3bc-2009 added LLDP discovery to standard Ethernet for maximum frame length (TLV subtype 4). [10] 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). [11]

Error detection

Errors in jumbo frames are more likely to go undetected by the simple CRC32 error detection of Ethernet and the simple additive checksums of UDP and TCP: as packet size increases, it becomes more likely that multiple errors cancel each other out. [lower-alpha 1]

One IETF approach for adopting jumbo frames avoids data integrity reduction of the service data unit by performing an extra CRC at the next network protocol layer above Ethernet. Stream Control Transmission Protocol (SCTP) transport (RFC 4960) and iSCSI (RFC 7143) use the Castagnoli CRC polynomial. 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. [13] 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 an increase of the Ethernet MTU would otherwise have resulted in a significant reduction in error detection.

Configuration

In networking equipment, maximum jumbo frame size may be specified using either maximum frame size (maximum layer 2 packet size, includes frame headers) or maximum transmission unit (maximum layer 3 packet size, excludes frame headers), depending on the equipment's configuration interface.[ citation needed ]

A network that has a mixture of devices configured for jumbo frames and devices not configured for jumbo frames may have performance issues. [14]

Bandwidth efficiency

Jumbo frames can increase the efficiency of Ethernet and network processing in hosts by reducing the protocol overhead, as shown in the following example with TCP over IPv4. The processing overhead of the hosts can potentially decrease by the ratio of the payload sizes (approximately six times improvement in this example). Whether this is significant depends on how packets are processed in the host. A host that uses its network interface controller's TCP offload engine with already reduced overhead receives less benefit than a host that processes frames with its CPU. The throughput by bandwidth efficiency can increase by 4.4%. [upper-alpha 1]

Frame-level bandwidth efficiency for TCP over IPv4
Frame type MTU Layer 1 overheadLayer 2 overheadLayer 3 overheadLayer 4 overheadPayload sizeTotal transmitted [upper-alpha 2] Efficiency [upper-alpha 3]
Standard1500 preamble
8 byte		 IPG
12 byte		 frame header
14 byte		 FCS
4 byte		 IPv4 header
20 byte		 TCP header
20 byte		1460 byte1538 byte94.93%
Jumbo9000preamble
8 byte		IPG
12 byte		frame header
14 byte		FCS
4 byte		IPv4 header
20 byte		TCP header
20 byte		8960 byte9038 byte99.14%
Other frame sizes for reference
IEEE 802.11 on A-MSDU [15] [16] 7935PLCP preamble & header
24 byte		IPG
varies		frame header & security ovhd
52 byte		FCS
4 byte		IPv4 header
20 byte		TCP header
20 byte		7895 byte8015 byte + IPG size< 98.5%
IEEE 802.11 bridged to standard Ethernet1500PLCP preamble & header
24 byte		IPG
varies		frame header & security ovhd
52 byte		FCS
4 byte		IPv4 header
20 byte		TCP header
20 byte		1460 byte1580 byte + IPG size< 92.4%
  1. ↑ 99.14%⁄94.93%-100%
  2. ↑ Total transmitted size is the sum of the payload size and all overhead sizes.
  3. ↑ Efficiency is calculated by dividing the payload size by the total transmitted size.

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. [17] Theoretically, as line bit rate increases, the packet payload size should increase in direct proportion to maintain equivalent timing parameters. This however implies the scaling of numerous intermediating logic circuits along the network path to accommodate the maximum frame size required.

Baby giant frames

Baby giant or baby jumbo frames are Ethernet frames that are only slightly larger than allowed by the IEEE Ethernet standards. [2] Baby giant frames are, for example, required for IP/MPLS over Ethernet to deliver Ethernet services with standard 1500 byte payloads. 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. [18] The increased overhead of extra MPLS and Ethernet headers means that the support for frames up to 1600 bytes is required in Carrier Ethernet networks. [19]

Jumbo frames for PPPoE is defined in RFC 4638, with the purpose of removing the old 1492-byte limit (originally defined because PPP needs 8 more bytes of overhead), so that normal 1500-byte Ethernet can run without fragmentation. The "PPP-Max-Payload" tag can still accommodate much larger, non-baby jumbo frames. [20]

Super jumbo frames

Super jumbo frames (SJFs) are frames that have a payload size over 9000 bytes. [21] 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 64,000 bytes, is under consideration.[ citation needed ] The main factor involved is an increase in the available memory buffer size in every intervening persistence mechanism along the path. Another important factor to consider is the further reduction of CRC32's effectiveness in detecting errors within even larger frame sizes.

The Total Length field of IPv4 and the Payload Length field of IPv6 each have a size of 16 bits, thus allowing data of up to 65535 octets . IPv6's jumbo payload option allows for up to 4  GiB (232-1 bytes) payload. These theoretical limits for the Internet Protocol (IP) MTU, however, are reached only on networks that have a suitable link-layer infrastructure.

Alternate approach

Large send offload and large receive offload offload per-frame processing making CPU load largely independent of frame size. It is another way to eliminate the per-packet overhead that jumbo frames were designed to reduce. [22] Jumbo frames are still useful from a bandwidth perspective, as they reduce the amount of bandwidth used for non-data overhead.

Notes

  1. ↑ Matt Mathis has discussed whether this is actually a practical problem, arguing that the reduced packet count for jumbo frames counteracts the higher undetected error rate. [12]

Related Research Articles

In computer networking, the maximum transmission unit (MTU) is the size of the largest protocol data unit (PDU) that can be communicated in a single network layer transaction. The MTU relates to, but is not identical to the maximum frame size that can be transported on the data link layer, e.g., Ethernet frame.

Network throughput refers to the rate of message delivery over a communication channel, such as Ethernet or packet radio, in a communication network. The data that these messages contain may be delivered over physical or logical links, or through network nodes. Throughput is usually measured in bits per second, and sometimes in data packets per second or data packets per time slot.

Carrier-sense multiple access with collision detection (CSMA/CD) is a medium access control (MAC) method used most notably in early Ethernet technology for local area networking. It uses carrier-sensing to defer transmissions until no other stations are transmitting. This is used in combination with collision detection in which a transmitting station detects collisions by sensing transmissions from other stations while it is transmitting a frame. When this collision condition is detected, the station stops transmitting that frame, transmits a jam signal, and then waits for a random time interval before trying to resend the frame.

A frame is a digital data transmission unit in computer networking and telecommunication. In packet switched systems, a frame is a simple container for a single network packet. In other telecommunications systems, a frame is a repeating structure supporting time-division multiplexing.

In telecommunications and computer networking, a network packet is a formatted unit of data carried by a packet-switched network. A packet consists of control information and user data; the latter is also known as the payload. Control information provides data for delivering the payload. Typically, control information is found in packet headers and trailers.

In the IEEE 802 reference model of computer networking, the logical link control (LLC) data communication protocol layer is the upper sublayer of the data link layer of the seven-layer OSI model. The LLC sublayer acts as an interface between the medium access control (MAC) sublayer and the network layer.

EtherType is a two-octet field in an Ethernet frame. It is used to indicate which protocol is encapsulated in the payload of the frame and is used at the receiving end by the data link layer to determine how the payload is processed. The same field is also used to indicate the size of some Ethernet frames.

The data link layer, or layer 2, is the second layer of the seven-layer OSI model of computer networking. This layer is the protocol layer that transfers data between nodes on a network segment across the physical layer. The data link layer provides the functional and procedural means to transfer data between network entities and may also provide the means to detect and possibly correct errors that can occur in the physical layer.

The Point-to-Point Protocol over Ethernet (PPPoE) is a network protocol for encapsulating Point-to-Point Protocol (PPP) frames inside Ethernet frames. It appeared in 1999, in the context of the boom of DSL as the solution for tunneling packets over the DSL connection to the ISP's IP network, and from there to the rest of the Internet. A 2005 networking book noted that "Most DSL providers use PPPoE, which provides authentication, encryption, and compression." Typical use of PPPoE involves leveraging the PPP facilities for authenticating the user with a username and password, via the PAP protocol or via CHAP. PAP was dominant in 2007 but service providers have been transitioning to the more secure CHAP, because PAP is a plain-text protocol. Around 2000, PPPoE was also starting to become a replacement method for talking to a modem connected to a computer or router over an Ethernet LAN displacing the older method, which had been USB. This use-case, connecting routers to modems over Ethernet is still extremely common today.

The maximum segment size (MSS) is a parameter of the Options field of the TCP header that specifies the largest amount of data, specified in bytes, that a computer or communications device can receive in a single TCP segment. It does not count the TCP header or the IP header. The IP datagram containing a TCP segment may be self-contained within a single packet, or it may be reconstructed from several fragmented pieces; either way, the MSS limit applies to the total amount of data contained in the final, reconstructed TCP segment.

TCP offload engine (TOE) is a technology used in some network interface cards (NIC) to offload processing of the entire TCP/IP stack to the network controller. It is primarily used with high-speed network interfaces, such as gigabit Ethernet and 10 Gigabit Ethernet, where processing overhead of the network stack becomes significant. TOEs are often used as a way to reduce the overhead associated with Internet Protocol (IP) storage protocols such as iSCSI and Network File System (NFS).

Throughput of a network can be measured using various tools available on different platforms. This page explains the theory behind what these tools set out to measure and the issues regarding these measurements.

In computer networking and telecommunications, TDM over IP (TDMoIP) is the emulation of time-division multiplexing (TDM) over a packet-switched network (PSN). TDM refers to a T1, E1, T3 or E3 signal, while the PSN is based either on IP or MPLS or on raw Ethernet. A related technology is circuit emulation, which enables transport of TDM traffic over cell-based (ATM) networks.

IEEE 802.1Q, often referred to as Dot1q, is the networking standard that supports virtual local area networking (VLANs) on an IEEE 802.3 Ethernet network. The standard defines a system of VLAN tagging for Ethernet frames and the accompanying procedures to be used by bridges and switches in handling such frames. The standard also contains provisions for a quality-of-service prioritization scheme commonly known as IEEE 802.1p and defines the Generic Attribute Registration Protocol.

A frame check sequence (FCS) is an error-detecting code added to a frame in a communication protocol. Frames are used to send payload data from a source to a destination.

In computer networks, goodput is the application-level throughput of a communication; i.e. the number of useful information bits delivered by the network to a certain destination per unit of time. The amount of data considered excludes protocol overhead bits as well as retransmitted data packets. This is related to the amount of time from the first bit of the first packet sent until the last bit of the last packet is delivered.

Path MTU Discovery (PMTUD) is a standardized technique in computer networking for determining the maximum transmission unit (MTU) size on the network path between two Internet Protocol (IP) hosts, usually with the goal of avoiding IP fragmentation. PMTUD was originally intended for routers in Internet Protocol Version 4 (IPv4). However, all modern operating systems use it on endpoints. In IPv6, this function has been explicitly delegated to the end points of a communications session. As an extension to the standard path MTU discovery, a technique called Packetization Layer Path MTU Discovery works without support from ICMP.

In computer networking, an Ethernet frame is a data link layer protocol data unit and uses the underlying Ethernet physical layer transport mechanisms. In other words, a data unit on an Ethernet link transports an Ethernet frame as its payload.

An IPv6 packet is the smallest message entity exchanged using Internet Protocol version 6 (IPv6). Packets consist of control information for addressing and routing and a payload of user data. The control information in IPv6 packets is subdivided into a mandatory fixed header and optional extension headers. The payload of an IPv6 packet is typically a datagram or segment of the higher-level transport layer protocol, but may be data for an internet layer or link layer instead.

Time-Sensitive Networking (TSN) is a set of standards under development by the Time-Sensitive Networking task group of the IEEE 802.1 working group. The TSN task group was formed in November 2012 by renaming the existing Audio Video Bridging Task Group and continuing its work. The name changed as a result of the extension of the working area of the standardization group. The standards define mechanisms for the time-sensitive transmission of data over deterministic Ethernet networks.

References

  1. ↑ "Ethernet Jumbo Frames" (PDF). Ethernet Alliance. 2009-11-12. Retrieved 2015-06-18.
  2. 1 2 "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
  3. ↑ "Ethernet Jumbo Frames" (PDF). EthernetAlliance.org. Retrieved April 28, 2017.
  4. ↑ 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.
  5. ↑ Foong, A; T. Huff; H. Hum; J. Patwardhan; G. Regnier (2003). "TCP Performance Re-visited". 2003 IEEE International Symposium on Performance Analysis of Systems and Software. ISPASS 2003. pp. 70–79. doi:10.1109/ISPASS.2003.1190234. ISBN   978-0-7803-7756-1. S2CID   17023487.
  6. ↑ D Murray; T Koziniec; K Lee; M Dixon (2012). "Large MTUs and internet performance". 2012 IEEE 13th International Conference on High Performance Switching and Routing. pp. 82–87. doi:10.1109/HPSR.2012.6260832. ISBN   978-1-4577-0833-6. S2CID   232321.
  7. ↑ Rick Summerhill (17 Feb 2003), rrsum-almes-mtu, Internet2
  8. ↑ Malahuwaish, Aos; Bakar, Kamalrulnizam; Ghafoor, Kayhan (2012). "A Congestion Avoidance Approach in Jumbo Frameenabled IP Network". International Journal of Advanced Computer Science and Applications. 3 (1): 69 – via ResearchGate.
  9. ↑ Scott Hogg (2013-03-06), Jumbo Frames, Network World , retrieved 2013-08-05, Most network devices support a jumbo frame size of 9216 bytes.
  10. ↑ IEEE 802.3 79.3.4 Maximum Frame Size TLV
  11. ↑ IEEE 802.3 3.2.7 MAC Client Data field
  12. ↑ Mathis, Matt (2016-10-08). "Arguments about Internet MTU". Archived from the original on 2016-10-08. Retrieved 2019-08-23.
  13. ↑ Philip Koopman. "32-Bit Cyclic Redundancy Codes for Internet Applications" (PDF). ECE Department & ICES, Carnegie Mellon University.
  14. ↑ "Guidance on the use of jumbo frames". Netgear . Retrieved 2020-03-21.
  15. ↑ Philip (October 20, 2016). "Wireless Network Speed Tweaks". speedguide.net. Retrieved October 20, 2016.
  16. ↑ IEEE 802.11-2012 8.2.3 General frame format
  17. ↑ Rutherford, W.; Jorgenson, L.; Siegert, M.; Van Epp, P.; Liu, L. (2007). "16000–64000 B pMTU experiments with simulation: The case for super jumbo frames at Supercomputing '05". Optical Switching and Networking. 4 (2): 121–130. doi:10.1016/j.osn.2006.10.001.
  18. ↑ RFC-3032, MPLS Label Stack Encoding
  19. ↑ "Ceragon, Jumbo Frames: The Microwave Perspective, Technical brief" (PDF). Archived from the original (PDF) on 2012-09-15.
  20. ↑ Arberg, P.; Kourkouzelis, D.; Duckett, M.; Anschutz, T.; Moisand, J. (September 2006). "Accommodating a Maximum Transit Unit/Maximum Receive Unit (MTU/MRU) Greater Than 1492 in the Point-to-Point Protocol over Ethernet (PPPoE)". doi: 10.17487/RFC4638 .{{cite journal}}: Cite journal requires |journal= (help)
  21. ↑ "Exploring the effects of jumbo frames" . Retrieved 2022-11-13.
  22. ↑ "Coding Relic: Requiem for Jumbo Frames". 2011-12-07. Retrieved 2011-12-07.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.