/openbmc/linux/Documentation/translations/zh_CN/infiniband/ |
H A D | ipoib.rst | 50 在数据报模式下,使用IB UD(不可靠数据报)传输,因此接口MTU等于IB L2 MTU 51 减去IPoIB封装头(4字节)。例如,在一个典型的具有2K MTU的IB结构中,IPoIB 52 MTU将是2048 - 4 = 2044字节。 55 允许MTU达到最大的IP包大小64K,这减少了处理大型UDP数据包、TCP段等所需的 60 小的UD MTU。
|
/openbmc/linux/tools/testing/selftests/bpf/ |
H A D | test_xsk.sh | 99 MTU=1500 128 ip link set ${VETH1} mtu ${MTU} 129 ip link set ${VETH0} mtu ${MTU} 175 cleanup_iface ${ETH} ${MTU} 191 cleanup_iface ${ETH} ${MTU}
|
/openbmc/linux/Documentation/infiniband/ |
H A D | ipoib.rst | 41 and so the interface MTU has is equal to the IB L2 MTU minus the 43 fabric with a 2K MTU, the IPoIB MTU will be 2048 - 4 = 2044 bytes. 47 transport and allows an MTU up to the maximal IP packet size of 64K, 55 networking stack to use the smaller UD MTU for these neighbours.
|
/openbmc/linux/Documentation/networking/ |
H A D | netdevices.rst | 185 MTU chapter 187 Each network device has a Maximum Transfer Unit. The MTU does not 190 than the mtu. The MTU does not include link layer header overhead, so 191 for example on Ethernet if the standard MTU is 1500 bytes used, the 198 packets based on the current MTU. 200 MTU is symmetrical and applies both to receive and transmit. A device 202 the MTU. A network device may use the MTU as mechanism to size receive
|
H A D | udplite.rst | 159 The checksum computation respects both buffersize and MTU. The size 171 The precise value also depends on the interface MTU. The interface MTU, 180 MTU: 1500 bytes Coverage Length: 856 bytes 197 MTU: 300 bytes Coverage length: 575 bytes 207 header). According to the interface MTU, these are split into 4 IP 213 MTU of 1280 bytes and a write buffer of 3356 bytes. If the checksum 214 coverage is less than 1232 bytes (MTU minus IPv6/fragment header
|
H A D | representors.rst | 64 link up/down, MTU, etc. For instance, bringing the representor 251 Setting an MTU on the representor should cause that same MTU to be reported to 253 (On hardware that allows configuring separate and distinct MTU and MRU values, 254 the representor MTU should correspond to the representee's MRU and vice-versa.)
|
/openbmc/openbmc-test-automation/extended/ |
H A D | standby_bmc.robot | 53 # Check if the ping works using 1400 MTU. 54 #Run Keyword if ${ping_status} == ${True} MTU Ping Test 161 MTU Ping Test 162 [Documentation] Ping test using MTU. 166 # mtu The maximum transmission unit (MTU) of a network interface.
|
/openbmc/openbmc/poky/meta/recipes-connectivity/bluez5/bluez5/ |
H A D | 0001-test-gatt-Fix-hung-issue.patch | 13 bt_gatt_server:MTU exchange complete, with MTU: 23
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/openconnect/openconnect/ |
H A D | 0001-Shim-for-renaming-of-GNUTLS_NO_EXTENSIONS-in-GnuTLS-.patch | 38 /* sets the DTLS MTU and returns the actual tunnel MTU */
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/netronome/ |
H A D | nfp.rst | 210 Configure interface Maximum Transmission Unit (MTU) 213 The MTU of interfaces can temporarily be set using the iproute2, ip link or 216 recommended as changes to the MTU using Network Manager can be made to 219 Set interface MTU to 9000 bytes:: 224 appropriate MTU values when handling jumbo frames or utilizing tunnels. For 226 egress a physical port, then the MTU of the VF should be set to lower than 229 the SmartNIC and the kernel then the user should also ensure that the PF MTU 338 * The packet Layer 3 length exceeds the device MTU.
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/intel/ |
H A D | fm10k.rst | 62 Jumbo Frames support is enabled by changing the Maximum Transmission Unit (MTU) 65 Use the ifconfig command to increase the MTU size. For example, enter the 76 permanent by adding 'MTU=9000' to the file: 81 NOTE: The maximum MTU setting for Jumbo Frames is 15342. This value coincides
|
H A D | igb.rst | 97 Jumbo Frames support is enabled by changing the Maximum Transmission Unit (MTU) 100 Use the ifconfig command to increase the MTU size. For example, enter the 111 permanent by adding 'MTU=9000' to the file: 116 NOTE: The maximum MTU setting for Jumbo Frames is 9216. This value coincides
|
H A D | e1000.rst | 198 on the MTU setting. The maximum MTU size is 16110. 201 MTU designates the frame size. It only needs to be set for Jumbo 397 Jumbo Frames support is enabled by changing the MTU to a value larger than 398 the default of 1500. Use the ifconfig command to increase the MTU size. 406 MTU=9000 419 - The maximum MTU setting for Jumbo Frames is 16110. This value coincides
|
/openbmc/linux/drivers/net/arcnet/ |
H A D | arc-rawmode.c | 49 if (length > MTU) in rx() 135 } else if (length > MTU) { in prepare_tx()
|
/openbmc/linux/Documentation/driver-api/mei/ |
H A D | mei.rst | 102 out_client_properties - Client Properties: MTU and Protocol Version. 114 max_msg_length (MTU) in client properties describes the maximum 115 data that can be sent or received. (e.g. if MTU=2K, can send 139 out_client_properties - Client Properties: MTU and Protocol Version.
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/neterion/ |
H A D | s2io.rst | 55 a. Jumbo frames. Xframe I/II supports MTU up to 9600 bytes, 119 a. Set MTU to maximum(9000 for switch setup, 9600 in back-to-back configuration) 122 For instance, for MTU=1500 a value of 210K has been observed to result in 128 For MTU=9000, TCP window size of 10 MB is recommended::
|
/openbmc/libmctp/docs/bindings/ |
H A D | vendor-ibm-astlpc.md | 64 ### MTU: Maximum Transmission Unit 67 Unit represents a value that is at least as large as the BTU. Negotiation of MTU 251 to the Baseline Transmission Unit, and the implementation assumes that the MTU 255 control region to negotiate the link MTU. Note that at the time that the MTU is 259 The relevant property that each endpoint must control is the MTU of packets it 267 both the BMC and the host have a consistent understanding of the MTU in each 398 … | ✓ | The host derives and writes to `rx_size` the packet size associated with its desired MTU |
|
/openbmc/linux/drivers/net/ethernet/huawei/hinic/ |
H A D | hinic_debugfs.c | 76 MTU, enumerator 120 case MTU: in hinic_dbg_get_func_table()
|
/openbmc/linux/Documentation/devicetree/bindings/net/ |
H A D | marvell-neta-bm.txt | 19 type is 'short'. For 'long' ones it would be overridden by port's MTU.
|
H A D | samsung-sxgbe.txt | 24 - max-frame-size: Maximum Transfer Unit (IEEE defined MTU), rather
|
/openbmc/u-boot/doc/device-tree-bindings/net/ |
H A D | ethernet.txt | 10 - max-frame-size: number, maximum transfer unit (IEEE defined MTU), rather than
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
H A D | counters.rst | 230 traffic. It might imply that the device MTU is larger than the software 236 larger than the MTU size. 571 size is larger than the MTU size. 920 peer connected to the adapter has a larger MTU configured. Using same MTU 925 - The number of dropped received packets due to length which exceed MTU 927 the peer connected to the adapter has a larger MTU configured. Using same 928 MTU configuration shall resolve this issue. 975 MTU size on a physical port. 981 implies that the peer connected to the adapter has a non-standard MTU 989 non-standard MTU configured.
|
/openbmc/linux/drivers/infiniband/ulp/ipoib/ |
H A D | Kconfig | 20 connections, and then increase the interface MTU with
|
/openbmc/linux/drivers/staging/qlge/ |
H A D | TODO | 1 * commit 7c734359d350 ("qlge: Size RX buffers based on MTU.", v2.6.33-rc1)
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/amazon/ |
H A D | ena.rst | 227 MTU chapter 230 The driver supports an arbitrarily large MTU with a maximum that is 231 negotiated with the device. The driver configures MTU using the 232 SetFeature command (ENA_ADMIN_MTU property). The user can change MTU
|