STRUCT ICC_BULK_DATA(9)
β¨ NAME β¨
struct icc_bulk_data β the little data bundle you use for bulk icc operations π
(also hiii, this is from the Kernel API Manual, section 9 β kernel API pages, we love to see it π«Ά)
πΈ SYNOPSIS πΈ
struct icc_bulk_data {
struct icc_path *path;
const char *name;
u32 avg_bw;
u32 peak_bw;
};
Bestie, that's the whole struct. Four little fields. Simple. Clean. Iconic. π
π Members π
pathβ a reference to the interconnect path. But ok so heads up π this one is internal use β that's not yours to poke at, iykyk, leave it alone, let it do its thing π§nameβ the name that comes from the"interconnect-names"DT property. Yes, that exact property, spelled exactly like that, lowercase with the dashes, no cap β¨avg_bwβ the average bandwidth, measured in icc units π¦peak_bwβ the peak bandwidth, also in icc units β same units, different vibe, bothu32π
Ngl the units matter:avg_bwandpeak_bware both in icc units, not bytes-per-whatever, so don't come for me with your own conversion math π
π₯ SEE ALSO π₯
- Kernel file
./include/linux/interconnect.hβ literally go read it, it's giving source of truth π
and that's the whole page, bestie β go forth and bulk your icc ops responsibly π
πΈ sign-off time: this gem comes from ./include/linux, dated October 2026, living under the name struct icc_bulk_data(9) β slay, see you in the next manpage ππβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms