ice_get_lan_q_ctx(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ice_get_lan_q_ctx β€” the Kernel API Manual page, but make it make sense πŸ’–

okay so first things first: this is the ice_get_lan_q_ctx(9) page out of the Kernel API Manual, and yes it's a kernel function page, but it's also lowkey the whole thing in two lines. it grabs the LAN queue context for a given VSI and TC. that's the entire vibe check. main character energy from a four-argument function, honestly πŸ’…


✨ NAME ✨

ice_get_lan_q_ctx β€” get the LAN queue context for the given VSI and TC πŸŽ€

like. that's it. that's the job. she finds your queue context and she slays.


πŸ¦‹ SYNOPSIS πŸ¦‹

here's the signature bestie, copy it exact, no "fixing" the spacing, i'm watching you πŸ‘€

struct ice_q_ctx * ice_get_lan_q_ctx (struct ice_hw *hw , u16 vsi_handle , u8 tc , u16 q_handle );

she returns a struct ice_q_ctx * and she takes four things. that's the whole exchange. four lil' arguments in, one queue context pointer out. no cap ✨


🌸 ARGUMENTS 🌸

not me having to read each one of these individually, but fine, we're doing it right, because details are the moment 🫢

  • hw β€” pointer to the HW struct. that's your hardware, your whole little silicon bestie. she needs to know which hardware we're talking about before anything else happens πŸ’–
  • vsi_handle β€” software VSI handle. the VSI in software-land, not the hardware one. iykyk, but if you don't: this is the software-side handle, exactly like it says 🌈
  • tc β€” TC number. just the number. of the TC. yes that's genuinely all the page tells you, and i refuse to invent more, because making stuff up is not the vibe πŸ™ˆ
  • q_handle β€” software queue handle. the queue handle, in software. the same species of thing as vsi_handle up there, but for a queue πŸ¦‹
ok real talk for a second: this page is short. like, two-paragraphs-and-a-huge-see-also-section short. so don't come for me about the length, come for the linked-list of related functions at the bottom instead πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

and now the main event, the group chat roster, the part where every single sibling function in ice_common.c shows up to the party. it's giving "family reunion where you have to greet everyone by name" 😭 but every single one of these is real and every single one gets a mention, so let's go.

the source file itself: ./drivers/net/ethernet/intel/ice/ice_common.c β€” that's the Kernel file, that's where she lives 🏠

πŸ’« the see-also squad, part 1

πŸŽ€ the see-also squad, part 2

🧚 the see-also squad, part 3

🌸 the see-also squad, part 4

πŸ”₯ the see-also squad, part 5

πŸ’œ the see-also squad, part 6

πŸ“ the see-also squad, part 7

⭐ the see-also squad, part 8

🌈 the see-also squad, part 9 (the finale, we made it)


okay that's genuinely everyone, i checked, twice, because missing one would be so embarrassing 😭 go read the ones you actually need and leave the rest on read, no judgment πŸ’…

and that's the page!! short function, long friend list, very "has 200 acquaintances and knows all their names" of her honestly πŸ‘‘

./drivers/net/ethernet/intel/ice Β· October 2026 β€” mwah, that's the source and the date, go forth and get your LAN queue context bestie, ily, bye 🫢✨

πŸ“¦ where this page comes from