__sbitmap_for_each_set(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

Okay bestie, welcome to the __sbitmap_for_each_set(9) page from the Kernel API Manual. We're gonna get through this together, and honestly? It's giving iconic. πŸ’…βœ¨


✨ NAME ✨

__sbitmap_for_each_set β€” iterate over each set bit in a &struct sbitmap. That's the whole vibe. Periodt. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

       void __sbitmap_for_each_set (struct sbitmap *sb , unsigned int start ,
       sb_for_each_fn fn , void *data );

πŸ’… ARGUMENTS πŸ’…

  • sb β€” the bitmap you're iterating over. It's the main character of this whole operation. πŸ’–
  • start β€” where you wanna start the iteration. Like, where the vibe check begins. ✨
  • fn β€” the callback, bestie. It should return true to continue, or false to break early. So if it returns false, you're out. No cap. πŸƒβ€β™€οΈπŸ’¨
  • data β€” a pointer that gets passed to the callback. It's the little care package you hand off. 🎧

🌸 DESCRIPTION 🌸

Okay so here's the tea: this function is inline even though it's non-trivial. Why? So that the function calls to the callback will hopefully get optimized away. It's giving "performance queen" and we stan. πŸ‘‘πŸ”₯


πŸ”₯ SEE ALSO πŸ”₯

Kernel file: ./include/linux/sbitmap.h


And that's the whole page, bestie! This one's brought to you by ./include/linux, dated October 2026. Stay slay, and remember: every set bit deserves to be iterated over. πŸ’–βœ¨πŸ«Ά

πŸ“¦ where this page comes from