axienet_change_mtu(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… axienet_change_mtu(9) β€” like, the MTU glow-up routine

okay so bestie, welcome to the Kernel API Manual ✨ β€” this is the page for axienet_change_mtu, and honestly? it's short, it's sweet, it does exactly one job and it does it flawlessly. main character energy fr fr πŸŽ€


🌸 NAME 🌸

axienet_change_mtu β€” the driver's change-MTU routine. that's it. that's the whole vibe. πŸ’–


✨ SYNOPSIS ✨

int axienet_change_mtu (struct net_device *ndev , int new_mtu );

like, you hand it a device and a number and it just... handles it. no drama. πŸ¦‹


🫢 ARGUMENTS 🫢

  • ndev β€” a pointer to the net_device structure. yes, that one. the one we've all been texting. πŸ’…
  • new_mtu β€” the brand-new MTU value you want applied. the whole reason you knocked on the door, ngl.

πŸ‘‘ RETURN πŸ‘‘

always returns 0 (success). no cap. every single time. it's giving "i don't miss" β€” 🌈⭐


πŸ’€ DESCRIPTION πŸ’€

so this is the change-MTU driver routine. here's the tea: it checks whether the Axi Ethernet hardware actually supports jumbo frames before it goes and changes the MTU. no vibes-based MTU changes here, we verify first. πŸ™ˆ

⚠️ lowkey important: this can be called only when the device is not up. like, device-down only. do not @ me if you ignore this. 😭

πŸ”₯ SEE ALSO πŸ”₯

kernel file: ./drivers/net/ethernet/xilinx/xilinx_axienet_main.c

and the whole friend group, in order because we're respectful like that:


k bye bestie, go change that MTU responsibly πŸ§šπŸ’œ β€” this page came from the source path ./drivers/net/ethernet/xilinx, dated October 2026, and yes that's the whole signature, mwah πŸ’‹

πŸ“¦ where this page comes from