ethnl_reply_header_size(9)
πΈ NAME πΈ
okay so welcome to the Kernel API Manual page for ethnl_reply_header_size(9), bestie π
ethnl_reply_header_sizeβ total size of reply header. that's the whole vibe. periodt π
β¨ SYNOPSIS β¨
unsigned int ethnl_reply_header_size (void );
π ARGUMENTS π
voidβ no arguments. none. zero. nada. it's giving mysterious and low-maintenance π«Ά
π¦ DESCRIPTION π¦
So this is an upper estimate, okay? The whole point is that we do not need to hold the RTNL lock longer than necessary β specifically, to prevent a rename between the size estimate and composing the message. iconic planning behavior honestly β¨
It accounts only for device ifindex and name, because those are the only attributes ethnl_fill_reply_header puts into the reply header. no cap πΈ
π SEE ALSO π
- Kernel file
./net/ethtool/netlink.hβ the home base π ethnl_strz_size(9)ethnl_put_strz(9)ethnl_update_u32(9)ethnl_update_u8(9)ethnl_update_u8_u32(9)ethnl_update_bool32(9)ethnl_update_bool(9)ethnl_update_binary(9)ethnl_update_bitfield32(9)struct ethnl_req_info(9)ethnl_req_get_phydev(9)struct ethnl_reply_data(9)struct ethnl_request_ops(9)
mwah π this cutie comes from source ./net/ethtool, dated October 2026, and it's literally ethnl_reply_header_size(9) β catch u later, bestie π«Άπ
π¦ 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