create_hdr_descs(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… create_hdr_descs(9) β€” from the Kernel API Manual, bestie ✨

okay so picture this: you're deep in create_hdr_descs(9) territory and you need somebody to just tell you what's happening. that's me. i got you. 🫢


🌸 NAME 🌸

create_hdr_descs β€” creates header and header extension descriptors. that's it. that's the whole vibe. ✨


πŸŽ€ SYNOPSIS πŸŽ€

int create_hdr_descs (u8 hdr_field , u8 *hdr_data , int len , int
*hdr_len , union sub_crq *scrq_arr );

copy it exactly, don't be cute with the spacing, she's particular about that πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • hdr_field β€” the bitfield that decides which headers you actually need. she's the one calling the shots, lowkey the main character of this function 😌
  • hdr_data β€” the buffer holding your header data. your data lives here. it's the moment. πŸ“
  • len β€” length of that data buffer. yes you have to know it. no you can't just guess. 😭
  • hdr_len β€” an array of the individual header lengths. each one gets its own lil slot, as they deserve πŸ‘‘
  • scrq_arr β€” the descriptor array. this is where everything lands. it's giving ✨destination✨

🌈 DESCRIPTION 🌈

so what does she do? she creates header and β€” if needed β€” header extension descriptors, and then places them in a descriptor array, scrq_arr. like, she builds the thing, she pops it in the array. no cap, that's the whole bit. πŸ”₯

"if needed" is doing real work in that sentence β€” header extension descriptors get made only when they're actually needed, not just for fun πŸ’œ

⭐ RETURN ⭐

the number of header descs. that's the return value, periodt. πŸ’…


🧚 SEE ALSO 🧚

the kernel file lives right here: ./drivers/net/ethernet/ibm/ibmvnic.c

and the whole friend group, in this exact order, bestie:


and that's the page, angels 🌸 sourcing this one from ./drivers/net/ethernet/ibm, dated October 2026 β€” mwah, go read some kernel code, ily πŸ’–πŸ‘‘

πŸ“¦ where this page comes from