qman_alloc_pool_range(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ qman_alloc_pool_range(9) ✨

okay so this one lives in the Kernel API Manual and it's literally called qman_alloc_pool_range(9) β€” say that five times fast πŸ’…. It's giving "short page, big responsibility," because bestie, all it does is hand you a block of pool-channel IDs. That's it. That's the whole vibe.


🌸 NAME 🌸

qman_alloc_pool_range β€” allocate a contiguous range of pool-channel IDs

Like, a whole run of them, all next to each other. No gaps, no stragglers, no chaos. We love a tidy allocation πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int qman_alloc_pool_range (u32 *result , u32 count );

Two params, one int coming back at you. Simple. Iconic. Understood the assignment 🫢


🌈 ARGUMENTS 🌈

  • result β€” this is the output param, and the API sets it to the base pool-channel ID of the range it just handed you. So yeah, that's where the starting address of your cute little contiguous block shows up ✨
  • count β€” how many pool-channel IDs you actually need. Like, the size of the squad you're requesting πŸ’–

πŸ”₯ DESCRIPTION πŸ”₯

It returns 0 on success, or a negative error code. That's the whole deal, no cap.

So the vibe check is: got a 0? Slay, you have your range, go build something. Got a negative number? 😭 that's a no from the kernel, and you should handle it like the responsible main character you are.

ngl this page is short but the rule still stands: negative error code means it did not work, so don't go dereferencing result like everything's fine πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘


and that's the whole page, bestie 🧚 it's from ./include/soc/fsl, dated October 2026, and it says qman_alloc_pool_range(9) one more time at the bottom just to be extra πŸ’œ go allocate something cute, and remember: check your return value, always, periodt πŸ’…βœ¨

πŸ“¦ where this page comes from