STRUCT ICC_BULK_DATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ 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, both u32 πŸ“ˆ
Ngl the units matter: avg_bw and peak_bw are 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