ice_aq_get_r...e_to_profile(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ice_aq_get_r...e_to_profile(9)

okay so this is a page from the Kernel API Manual, and honestly? it's giving "tiny function, huge friend group" energy. literally one call, and it's plugged into like a hundred other functions. main character behavior fr fr.


✨ NAME ✨

ice_aq_get_recipe_to_profile β€” map a recipe to a packet profile πŸŽ€

like, it's the little matchmaker that hooks a recipe up with its profile. wingwoman energy, no cap.


🌸 SYNOPSIS 🌸

int ice_aq_get_recipe_to_profile (struct ice_hw *hw , u32 profile_id ,
       u64 *r_assoc , struct ice_sq_cd *cd );

returns an int, bestie. remember that. πŸ’–


πŸ¦‹ ARGUMENTS πŸ¦‹

  • hw β€” pointer to the HW struct. your hardware babygirl. she's the context for literally everything here.
  • profile_id β€” the package profile ID that you're associating the recipe with. this is the "who are we setting up with whom" part of the operation. πŸ’…
  • r_assoc β€” the Recipe bitmap, filled in for you, and you need to return it as the response. so it's like β€” the function fills the bucket, but you have to carry it home. 🫢
  • cd β€” pointer to the command details structure, or NULL. and this one is also doing double duty: it associates the profile ID with the given recipe, opcode 0x0293. iykyk. ✨

πŸ”₯ SEE ALSO πŸ”₯

okay this is the part where i need you to sit down, because the friend group is ENORMOUS and we're listing every single one of them, no skipping, periodt:

kernel file: ./drivers/net/ethernet/intel/ice/ice_switch.c πŸ‘‘

yeah. all of them. every last one. πŸ’€πŸ†


ngl bestie, one important note before you go: this page lives in the kernel source tree at ./drivers/net/ethernet/intel/ice, so head there if you want to snoop the actual code. 🧚

and that's the whole page, babes! πŸ“ this lil beauty is from the Kernel API Manual, sourced out of ./drivers/net/ethernet/intel/ice, dated October 2026 β€” go forth and map those recipes to those profiles, you absolute icon. πŸ’œπŸŒˆβœ¨

πŸ“¦ where this page comes from