STRUCT ICC_REQ(9)

💖 NAME 💖

okay so bestie, this is struct icc_req(9) from the Kernel API Manual, and it is literally the constraints that are attached to each node. that's the assignment, periodt. 💅

🦋 SYNOPSIS 🦋

the whole struct ate, no notes. exact shape:

       struct icc_req {
           struct hlist_node req_node;
           struct icc_node *node;
           struct device *dev;
           bool enabled;
           u32 tag;
           u32 avg_bw;
           u32 peak_bw;
        };

🎀 Members 🎀

field-by-field vibe check, bestie:

• req_node — entry in list of requests for the particular node. list-link realness, but make it kernel.
• node — the interconnect node to which this constraint applies. main character pointer energy.
• dev — reference to the device that sets the constraints. whose vibe is this? this device's vibe.
• enabled — indicates whether the path with this request is enabled. yes/no energy, but the field is bool.
• tag — path tag, and yes it's optional.
• avg_bw — an integer describing the average bandwidth in kBps.
• peak_bw — an integer describing the peak bandwidth in kBps.

🌈 SEE ALSO 🌈

go peek at the Kernel file ./drivers/interconnect/internal.h, and also struct icc_path(9) — both on the iconic reading list. iykyk 🫶

💖 that's the vibe check, bestie — this page came from ./drivers/interconnect, October 2026. slay. 💖