emac_xdp_xmit(9)

📦 version 7.3.1, in nixpkgs unstable

💅 emac_xdp_xmit(9) — from the Kernel API Manual, bestie ✨

okay so listen. this is a page straight out of the Kernel API Manual, and it's about one little function that does a very specific job. stay with me, it's gonna be cute and it's gonna be correct 💖

🌸 NAME 🌸

emac_xdp_xmit — the function that implements ndo_xdp_xmit. that's it, that's the whole vibe. it's the ndo_xdp_xmit implementation, no cap 🫶

✨ SYNOPSIS ✨

int emac_xdp_xmit (struct net_device *dev , int n , struct xdp_frame
**frames , u32 flags );

yes she takes four things and returns an int, periodt 💅

🎀 ARGUMENTS 🎀

  • dev — the netdev. that's the network device we're doing all this on 🦋
  • n — number of frames. literally just how many frames we're talking about ⭐
  • frames — array of XDP buffer pointers. it's giving "here's the whole lineup" 👑
  • flags — XDP extra info. the lil extras, yk? 🌈

🔥 RETURN 🔥

the number of frames successfully sent 🎉 and like — failed frames will be free'ed by XDP core. so don't you dare go freeing them yourself, that's not your job, that's XDP core's job 🙈

💜 DESCRIPTION 💜

so for error cases? a negative errno code comes back and no-frames are transmitted. read that again bestie, because it matters: the caller must handle freeing frames in that situation 😭 the caller. that's you. handle it.

🧚 SEE ALSO 🧚

the kernel file it lives in, for the curious girlies:

Kernel file ./drivers/net/ethernet/ti/icssg/icssg_prueth.c

and the whole friend group of related pages — every single one, i'm not skipping anybody:

💀 friendly reminder: negative errno = nothing went out + the caller frees the frames. that's the whole caveat. don't fumble it.

and that's the page, bestie 🍓 this one came from ./drivers/net/ethernet/ti/icssg, dated October 2026 — mwah, go ship some frames 💖✨🎀🦋

📦 where this page comes from