msc_buffer_iterate(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, welcome to the msc_buffer_iterate(9) page from the Kernel API Manual ✨ This is the one about the function that goes through multiblock buffer's data, and it is iconic in a deeply kernel-core way πŸ’…

msc_buffer_iterate β€” go through multiblock buffer's data.

πŸ¦‹ SYNOPSIS πŸ¦‹

ssize_t msc_buffer_iterate (struct msc_iter *iter , size_t size , void
       *data , unsigned long (*fn)(void *, void *, size_t) );

πŸŽ€ ARGUMENTS πŸŽ€

  • iter β€” iterator structure. the iterator bestie in question.
  • size β€” amount of data to scan. literally how much data we're scanning, periodt.
  • data β€” callback's private data. the callback's private stash.
  • fn β€” iterator callback. the callback main character.

πŸ’– DESCRIPTION πŸ’–

This will start at the window which will be written to next (containing the oldest data) and work its way to the current window, calling fn for each chunk of data as it goes. chunk by chunk, callback by callback β€” it’s giving oldest-to-current energy, fr fr.

πŸ”₯ caller caveat, bestie: Caller should have msc::user_count reference to make sure the buffer doesn't disappear from under us. like, do not skip this.

⭐ RETURN ⭐

amount of data actually scanned. That's the return value β€” the actual scanned amount, not the vibe estimate 😌

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/hwtracing/intel_th/msu.c β€” plus this whole linked-up squad, iykyk:


xoxo, bestie 🫢 source/version: ./drivers/hwtracing/intel_th Β· date: October 2026 πŸ’–

πŸ“¦ where this page comes from