xgmac_change_mtu(9)
β¨ bestie, welcome to the xgmac_change_mtu(9) page β this is the Kernel API Manual and we're gonna make MTU changes make sense π
πΈ NAME πΈ
xgmac_change_mtuβ entry point to change MTU size for the device. literally the glow-up portal for your device's MTU π«Ά
β¨ SYNOPSIS β¨
int xgmac_change_mtu (struct net_device *dev , int new_mtu );
π ARGUMENTS π
devβ device pointer. yes bestie, the device pointer πnew_mtuβ the new MTU size for the device. the fresh MTU value in question β¨
π¦ DESCRIPTION π¦
okay so the Maximum Transfer Unit (MTU) is used by the network layer to drive packet transmission. no cap, that's its whole job.
Ethernet has an MTU of 1500 octets (ETH_DATA_LEN). that's the default vibe.
This value can be changed with ifconfig. main character energy fr fr.
Return value: 0 on success and an appropriate (-)ve integer as defined in errno.h file on failure. so yeah, success is 0, failure gives you the appropriate negative integer situation π
π SEE ALSO π
- Kernel file
./drivers/net/ethernet/calxeda/xgmac.c xgmac_dma_desc_rings_init(9)xgmac_tx_complete(9)xgmac_open(9)xgmac_stop(9)xgmac_xmit(9)xgmac_poll(9)xgmac_tx_timeout(9)xgmac_set_rx_mode(9)xgmac_probe(9)xgmac_remove(9)
source/version: ./drivers/net/ethernet/calxeda Β· date: October 2026 Β· page: xgmac_change_mtu(9) β byeee bestie, go slay that MTU π
π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms