| /linux-4.4.14/Documentation/networking/ |
| D | netdevices.txt | 23 MTU
25 Each network device has a Maximum Transfer Unit. The MTU does not
28 than the mtu. The MTU does not include link layer header overhead, so
29 for example on Ethernet if the standard MTU is 1500 bytes used, the
36 packets based on the current MTU.
38 MTU is symmetrical and applies both to receive and transmit. A device
40 the MTU. A network device may use the MTU as mechanism to size receive
|
| D | udplite.txt | 152 The checksum computation respects both buffersize and MTU. The size
164 The precise value also depends on the interface MTU. The interface MTU,
173 MTU: 1500 bytes Coverage Length: 856 bytes
190 MTU: 300 bytes Coverage length: 575 bytes
200 header). According to the interface MTU, these are split into 4 IP
206 MTU of 1280 bytes and a write buffer of 3356 bytes. If the checksum
207 coverage is less than 1232 bytes (MTU minus IPv6/fragment header
|
| D | s2io.txt | 40 a. Jumbo frames. Xframe I/II supports MTU up to 9600 bytes,
89 a. Set MTU to maximum(9000 for switch setup, 9600 in back-to-back configuration)
91 For instance, for MTU=1500 a value of 210K has been observed to result in
95 For MTU=9000, TCP window size of 10 MB is recommended.
|
| D | igb.txt | 44 Jumbo Frames support is enabled by changing the MTU to a value larger than
45 the default of 1500. Use the ip command to increase the MTU size.
54 - The maximum MTU setting for Jumbo Frames is 9216. This value coincides
|
| D | ixgb.txt | 136 depending on the MTU setting. When the MTU size is 1500 or less, the
137 receive buffer size is 2048 bytes. When the MTU is greater than 1500 the
139 maximum MTU size is 16114.
201 # set the MTU (max transmission unit) - it requires your switch and clients
299 enabled by changing the MTU to a value larger than the default of 1500.
300 The maximum value for the MTU is 16114. Use the ip command to
301 increase the MTU size. For example:
305 The maximum MTU setting for Jumbo Frames is 16114. This value coincides
|
| D | e1000.txt | 180 on the MTU setting. The maximum MTU size is 16110.
182 NOTE: MTU designates the frame size. It only needs to be set for Jumbo
398 Jumbo Frames support is enabled by changing the MTU to a value larger than
399 the default of 1500. Use the ifconfig command to increase the MTU size.
407 MTU=9000
420 - The maximum MTU setting for Jumbo Frames is 16110. This value coincides
|
| D | ieee802154.txt | 117 The IEEE 802.15.4 standard specifies an MTU of 127 bytes, yielding about 80
124 to support the IPv6 minimum MTU requirement [RFC2460], and stateless header
|
| D | ipsec.txt | 19 MTU.
|
| D | ixgbe.txt | 215 enabled by changing the MTU to a value larger than the default of 1500.
216 The maximum value for the MTU is 16110. Use the ip command to
217 increase the MTU size. For example:
221 The maximum MTU setting for Jumbo Frames is 9710. This value coincides
|
| D | vxge.txt | 41 X3100 Series supports MTU up to 9600 bytes, modifiable using
|
| D | netdev-features.txt | 152 headers. Some drivers set this because the cards can't handle the bigger MTU.
153 [FIXME: Those cases could be fixed in VLAN code by allowing only reduced-MTU
|
| D | cops.txt | 43 UP BROADCAST RUNNING NOARP MULTICAST MTU:600 Metric:1
|
| D | e1000e.txt | 249 Jumbo Frames support is enabled by changing the MTU to a value larger than
250 the default of 1500. Use the ifconfig command to increase the MTU size.
259 - The maximum MTU setting for Jumbo Frames is 9216. This value coincides
|
| D | ip-sysctl.txt | 19 Disable Path MTU Discovery. If enabled in mode 1 and a
22 to raise min_pmtu to the smallest interface MTU on your system
25 In mode 2 incoming Path MTU Discovery messages will be
36 TCP path mtu must still work but path MTU information of other
44 default 552 - minimum discovered Path MTU
110 The advertised MSS depends on the first hop route MTU, but will
223 Path MTU discovery (MTU probing). If MTU probing is enabled,
402 Controls TCP Packetization-Layer Path MTU Discovery. Takes three
409 Controls how often to start TCP Packetization-Layer Path MTU
414 Controls when TCP Packetization-Layer Path MTU Discovery probing
[all …]
|
| D | eql.txt | 106 for your machine, and the MTU you prefer for your SLIP lines. One
107 could argue that MTU should be roughly half the usual size for two
|
| D | can.txt | 414 unit (MTU) of the CAN(FD) network interface and skbuff data length. Two
584 /* the content can be handled independently from the received MTU size */
606 The CAN device MTU can be retrieved e.g. with a SIOCGIFMTU ioctl() syscall.
1182 devices maximum transfer unit (MTU):
1184 MTU = 16 (CAN_MTU) => sizeof(struct can_frame) => 'legacy' CAN device
1185 MTU = 72 (CANFD_MTU) => sizeof(struct canfd_frame) => CAN FD capable device
1187 The CAN device MTU can be retrieved e.g. with a SIOCGIFMTU ioctl() syscall.
1198 option also switches the device MTU to 72 (CANFD_MTU).
|
| D | arcnet.txt | 323 LANMAN. Because the MTU of 493 is actually smaller than the
330 MTU that does it.)
337 RFC1201's packet splitting, and the MTU of 507 is still
|
| D | cdc_mbim.txt | 269 - no IPS or DSS session can use a frame size greater than the MTU on
|
| D | packet_mmap.txt | 42 enabled. For transmission, check the MTU (Maximum Transmission Unit) used and
|
| D | rxrpc.txt | 938 The maximum packet MTU size that we're willing to receive in bytes. This
|
| D | bonding.txt | 1758 UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
1764 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
1771 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
|
| D | arcnet-hardware.txt | 66 of 576 bytes, let alone the Ethernet MTU of 1500. To compensate, an extra
|
| /linux-4.4.14/Documentation/infiniband/ |
| D | ipoib.txt | 37 and so the interface MTU has is equal to the IB L2 MTU minus the
39 fabric with a 2K MTU, the IPoIB MTU will be 2048 - 4 = 2044 bytes.
43 transport and allows an MTU up to the maximal IP packet size of 64K,
51 networking stack to use the smaller UD MTU for these neighbours.
|
| D | sysfs.txt | 86 vl2mtu/ - 16 (0 - 15) files used to determine MTU for vl
|
| /linux-4.4.14/drivers/net/arcnet/ |
| D | arc-rawmode.c | 49 if (length > MTU) in rx()
135 } else if (length > MTU) { in prepare_tx()
|
| D | rfc1051.c | 229 } else if (length > MTU) { in prepare_tx()
|
| D | arcdevice.h | 135 #define MTU 253 /* normal packet max size */ macro
|
| D | capmode.c | 159 } else if (length > MTU) { in prepare_tx()
|
| D | rfc1201.c | 453 } else if (softlen > MTU) { /* exception packet - add an extra header */ in load_pkt()
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | samsung-sxgbe.txt | 27 - max-frame-size: Maximum Transfer Unit (IEEE defined MTU), rather
|
| D | ethernet.txt | 10 - max-frame-size: number, maximum transfer unit (IEEE defined MTU), rather than
|
| /linux-4.4.14/drivers/infiniband/ulp/ipoib/ |
| D | Kconfig | 19 connections, and then increase the interface MTU with
|
| /linux-4.4.14/Documentation/misc-devices/mei/ |
| D | mei.txt | 113 out_client_properties - Client Properties: MTU and Protocol Version.
124 max_msg_length (MTU) in client properties describes the maximum
125 data that can be sent or received. (e.g. if MTU=2K, can send
|
| /linux-4.4.14/net/sctp/ |
| D | Kconfig | 23 -- data fragmentation to conform to discovered path MTU size,
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-class-net-mesh | 41 packet size exceeds the outgoing interface MTU.
|
| D | sysfs-class-net-statistics | 98 (e.g: larger than MTU). See the network driver for the exact
|
| D | sysfs-class-net | 176 Indicates the interface currently configured MTU value, in
|
| /linux-4.4.14/drivers/clocksource/ |
| D | Kconfig | 85 Support for Multi Timer Unit. MTU provides access
|
| /linux-4.4.14/net/netfilter/ |
| D | Kconfig | 926 connection (usually limiting it to your outgoing interface's MTU
|
| /linux-4.4.14/Documentation/s390/ |
| D | Debugging390.txt | 2062 UP BROADCAST RUNNING MULTICAST MTU:2000 Metric:1
|