libeth_xdpsq_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME

Okay so bestie, this page is straight outta the Kernel API Manual, and it’s all about libeth_xdpsq_get. She initializes &libeth_xdpsq_lock β€” yes, that’s the whole name line, and no, we’re not skipping a single crumb. πŸŽ€

✨ SYNOPSIS ✨

Behold, the signature:

void libeth_xdpsq_get (struct libeth_xdpsq_lock *lock , const struct
net_device *dev , bool share );

🫢 ARGUMENTS 🫢

  • lock β€” the lock to initialize. Main character lock behavior. πŸ’…
  • dev β€” the netdev which this lock belongs to. πŸ¦‹
  • share β€” whether XDPSQs can be shared. 🫢

πŸ’– DESCRIPTION πŸ’–

Okay so what’s tea? libeth_xdpsq_get tracks the current XDPSQ association and enables the static lock if needed. That’s the whole flex β€” association tracking + static lock enabling when needed. Periodt. ✨

πŸ‘‘ SEE ALSO πŸ‘‘

If you’re in your kernel-doc rabbit hole era, here’s the whole squad:


Okay that’s the whole page, bestie πŸ«ΆπŸ’–. Source/version vibes: ./include/net/libeth, dated October 2026. Go be iconic with your XDPSQs. πŸ‘‘βœ¨

πŸ“¦ where this page comes from