xdp_buff_add_frag(9)
π NAME π
xdp_buff_add_frag β the one that attaches a frag to &xdp_buff, bestie π
β¨ SYNOPSIS β¨
okay so picture this in the Kernel API Manual, section 9, and it looks exactly like this:
bool xdp_buff_add_frag (struct xdp_buff *xdp , netmem_ref netmem , u32
offset , u32 size , u32 truesize );
πΈ ARGUMENTS πΈ
xdpβ the XDP buffer you're attaching the frag to π«Άnetmemβ the network memory that's holding the fragoffsetβ the offset where the frag startssizeβ how big the frag istruesizeβ the total memory size the frag occupies
π¦ DESCRIPTION π¦
So this is the version of __xdp_buff_add_frag that takes care of the pfmemalloc bit for you π« like, same energy, it just handles that bit so you don't have to. Obsessed, honestly.
π₯ RETURN π₯
trueβ success, we ate πfalseβ there's no space for the frag in the shared info struct π
π SEE ALSO π
- Kernel file
./include/net/xdp.h XDP RX-queue information(9)__xdp_buff_add_frag(9)xdp_rxq_info_attach_mem_model(9)xdp_rxq_info_detach_mem_model(9)
and that's the whole page, bestie π«Ά mwah π β it calls ./include/net home, it's dated October 2026, and if you ever lose it in the group chat it's filed under xdp_buff_add_frag(9). periodt β¨
π¦ 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