libeth_xdpsq_shared(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

ok so libeth_xdpsq_shared β€” this is the libeth_xdpsq_shared(9) page btw, from the Kernel API Manual β€” and it's literally just answering one question: can XDPSQs be shared between several CPUs or not?? that's the whole vibe check πŸ¦‹


✨ SYNOPSIS ✨

bool libeth_xdpsq_shared (u32 num );

πŸŽ€ ARGUMENTS πŸŽ€

  • num β€” the number of active XDPSQs, bestie. that's the count of ones currently doing their thing πŸ’…

🌸 RETURN 🌸

it hands you back true if there's no 1:1 XDPSQ/CPU association β€” like, the pairing is not exclusive, iykyk β€” and false otherwise 🫢

ngl this is the entire function. no cap, that's it, that's the whole thing 😭 go forth and vibe

πŸ¦‹ SEE ALSO πŸ¦‹

okay this part is giving main character energy because the list is LONG, buckle up bestie 🎒 β€” Kernel file ./include/net/libeth/xdp.h struct libeth_xdp_buff(9), __LIBETH_XDP_ONSTACK_BUFF(9), LIBETH_XDP_ONSTACK_BUFF(9), libeth_xdpsq_num(9), libeth_xdpsq_id(9), libeth_xdpsq_get(9), libeth_xdpsq_put(9), libeth_xdpsq_lock(9), libeth_xdpsq_unlock(9), libeth_xdpsq_deinit_timer(9), libeth_xdpsq_queue_timer(9), libeth_xdpsq_run_timer(9), enum (anonymous)(9), enum (anonymous)(9), struct libeth_xdp_tx_frame(9), struct libeth_xdp_tx_bulk(9), LIBETH_XDP_ONSTACK_BULK(9), struct libeth_xdpsq(9), struct libeth_xdp_tx_desc(9), libeth_xdp_ptr_to_priv(9), libeth_xdp_priv_to_ptr(9), libeth_xdp_tx_xmit_bulk(9), libeth_xdp_tx_queue_head(9), libeth_xdp_tx_queue_frag(9), libeth_xdp_tx_queue_bulk(9), libeth_xdp_tx_fill_stats(9), libeth_xdp_tx_fill_buf(9),

__libeth_xdp_tx_flush_bulk(9), libeth_xdp_tx_flush_bulk(9), libeth_xdp_xmit_init_bulk(9), libeth_xdp_xmit_frame_dma(9), libeth_xdp_xmit_queue_head(9), libeth_xdp_xmit_queue_frag(9), libeth_xdp_xmit_queue_bulk(9), libeth_xdp_xmit_fill_buf(9), libeth_xdp_xmit_flush_bulk(9), __libeth_xdp_xmit_do_bulk(9), libeth_xdp_xmit_do_bulk(9), libeth_xdp_tx_init_bulk(9), libeth_xdp_init_buff(9), libeth_xdp_save_buff(9), libeth_xdp_return_stash(9), libeth_xdp_return_buff(9), libeth_xdp_prepare_buff(9), libeth_xdp_process_buff(9), libeth_xdp_buff_stats_frags(9), __libeth_xdp_run_prog(9), __libeth_xdp_run_flush(9), libeth_xdp_run_prog(9), __libeth_xdp_run_pass(9), libeth_xdp_run_pass(9), libeth_xdp_finalize_rx(9), LIBETH_XDP_DEFINE_TIMER(9), LIBETH_XDP_DEFINE_FLUSH_TX(9), LIBETH_XDP_DEFINE_FLUSH_XMIT(9), LIBETH_XDP_DEFINE_RUN_PROG(9), LIBETH_XDP_DEFINE_RUN_PASS(9),

LIBETH_XDP_DEFINE_RUN(9), LIBETH_XDP_DEFINE_FINALIZE(9), libeth_xdp_buff_to_rq(9), libeth_xdpmo_rx_hash(9), __libeth_xdp_complete_tx(9), libeth_xdp_set_features(9), libeth_xdp_set_features_noredir(9) πŸ”₯

πŸ’€ yes enum (anonymous)(9) really is in there twice. not me editing the source, we keep it exactly as it is, periodt.

and that's the whole page bestie, tysm for reading πŸŽ€ this iconic little number lives at ./include/net/libeth, dated October 2026, and it answers to the name libeth_xdpsq_shared(9) β€” slay, go read it again, it's short πŸ’œβœ¨

πŸ“¦ where this page comes from