libeth_xsk_run_prog(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… libeth_xsk_run_prog β€” Kernel API Manual energy ✨

okay so bestie, we're deep in the kernel networking lore rn and this one's called libeth_xsk_run_prog(9) β€” it lives in the Kernel API Manual and it's literally the "run the XDP program on the XSk path and deal with every single verdict" girlie πŸŽ€


✨ SYNOPSIS ✨

libeth_xsk_run_prog (xdp , bq , fl );

like, three args, no drama πŸ’œ


🫢 ARGUMENTS 🫢

  • xdp β€” the XSk buffer you want processed. that's the main character of this call, no cap 🌸
  • bq β€” the XDP Tx bulk where all the XDP_TX buffers get queued up πŸ¦‹
  • fl β€” the driver's XDP_TX bulk flush callback. she's the one who actually flushes it πŸ’…

πŸ’– DESCRIPTION πŸ’–

so what she does is: run the attached XDP program, and then handle all the possible verdicts that come back. every. single. one. 😭

and lowkey the move here is β€” prefer using it via LIBETH_XSK_DEFINE_RUN{,_PASS,_PROG}() instead of calling it raw. iykyk πŸ”₯


⭐ RETURN ⭐

returns a libeth_xdp prog verdict, which depends entirely on whatever verdict the prog itself gave back. it's giving "you get what you give" ✨


πŸŽ€ SEE ALSO πŸŽ€

the kernel file is ./include/net/libeth/xsk.h, and then the whole friend group:

go read the whole squad honestly, they all ate πŸ‘‘

k bye bestie, this page was brought to you from ./include/net/libeth and stamped October 2026 β€” stan the kernel docs, mwah πŸ’‹πŸŒˆ

πŸ“¦ where this page comes from