STRUCT LLCC_SLICE_CONFIG(9)

💖 NAME 💖

Hiii bestie 🫶 welcome to struct llcc_slice_config(9) from the Kernel API Manual. This is literally the data associated with the LLCC slice — the struct that carries all the slice config vibes ✨.

✨ SYNOPSIS ✨

struct llcc_slice_config {
    u32 usecase_id;
    u32 slice_id;
    u32 max_cap;
    u32 priority;
    bool fixed_size;
    u32 bonus_ways;
    u32 res_ways;
    u32 cache_mode;
    u32 probe_target_ways;
    bool dis_cap_alloc;
    bool retain_on_pc;
    bool activate_on_init;
    bool write_scid_en;
    bool write_scid_cacheable_en;
    bool stale_en;
    bool stale_cap_en;
    bool mru_uncap_en;
    bool mru_rollover;
    bool alloc_oneway_en;
    bool ovcap_en;
    bool ovcap_prio;
    bool vict_prio;
    u32 parent_slice_id;
};

🌸 Members 🌸

Okay so here's the member-by-member tea, and every single field is staying exactly where it is 💅:

• usecase_id — unique id for the client's use case.
• slice_id — LLCC slice id for each client.
• max_cap — the maximum capacity of the cache slice, provided in KB.
• priority — priority of the client, used to select the victim line for replacement.
• fixed_size — boolean indicating if the slice has a fixed capacity.
• bonus_ways — bonus ways are additional ways to be used for any slice if the client ends up using more than the reserved cache ways. Bonus ways are allocated only if they are not reserved for some other client.
• res_ways — reserved ways for the cache slice; the reserved ways cannot be used by any other client than the one they're assigned to.
• cache_mode — each slice operates as a cache, and this controls the mode of the slice: normal or TCM(Tightly Coupled Memory).
• probe_target_ways — determines what ways to probe for access hit. When configured to 1, only bonus and reserved ways are probed. When configured to 0, all ways in LLCC are probed.
• dis_cap_alloc — disable capacity based allocation for a client.
• retain_on_pc — if this bit is set and the client has maintained active vote, then the ways assigned to this client are not flushed on power collapse.
• activate_on_init — activate the slice immediately after it is programmed.
• write_scid_en — bit enables write cache support for a given scid.
• write_scid_cacheable_en — enables write cache cacheable support for a given scid (not supported on v2 or older hardware).
• stale_en — bit enables stale.
• stale_cap_en — bit enables stale only if current scid is over-cap.
• mru_uncap_en — roll-over on reserved cache ways if current scid is under-cap.
• mru_rollover — roll-over on reserved cache ways.
• alloc_oneway_en — always allocate one way on over-cap even if there's no same-scid lines for replacement.
• ovcap_en — once current scid is over-capacity, allocate other over-cap SCID.
• ovcap_prio — once current scid is over-capacity, allocate other low priority over-cap scid. Depends on corresponding bit being set in ovcap_en.
• vict_prio — when current scid is under-capacity, allocate over other lower-than victim priority-line threshold scid.
• parent_slice_id — for grouped slices, specifies the slice id of the parent.

🦋 SEE ALSO 🦋

• Kernel file ./drivers/soc/qcom/llcc-qcom.c
• llcc_slice_getd(9)
• llcc_slice_putd(9)
• llcc_slice_activate(9)
• llcc_slice_deactivate(9)
• llcc_get_slice_id(9)
• llcc_get_slice_size(9)

That's the whole page, bestie 💖 source/version vibes: ./drivers/soc/qcom and struct llcc_slice_config(9); date: October 2026 — cute lil footer sign-off complete, byeee 🦋✨