lc_get_cumulative(9)

✨ lc_get_cumulative 💅

okay so bestie, welcome to the kernel API manual for lc_get_cumulative(9) — yes that (9) means it's a kernel thing, we're in the big leagues now 🎀

---

🌸 NAME 🌸

lc_get_cumulative — it's literally lc_get but with a glow-up: it also finds the elements that are about to be changed 👑

---

🦋 SYNOPSIS 🦋

struct lc_element * lc_get_cumulative (struct lru_cache *lc , unsigned
int enr );

---

💖 ARGUMENTS 💖

• lc — the lru cache we're operating on, bestie. that's the whole vibe check target 🎯
• enr — the label to look up. the thing we're hunting for 🔍

---

✨ DESCRIPTION ✨

so here's the tea ☕ — unlike lc_get, this one also returns the element for enr if it belongs to a pending transaction. so the return values are exactly like the ones for lc_get, plus this extra one:

pointer to an element that's already chillin' on the "to_be_changed" list. and in this case, the cache was already marked LC_DIRTY. no cap, it's flagged 💀

and now the important part, bestie, listen up 🫶 — the caller needs to make sure that the pending transaction is completed before proceeding to actually use this element. like, don't touch it until the transaction's done, fr fr. periodt.

---

🌈 SEE ALSO 🌈

kernel file ./lib/lru_cache.c — the source of truth, go read it iykyk 📖

• lc_create(9)
• lc_destroy(9)
• lc_reset(9)
• lc_seq_printf_stats(9)
• lc_find(9)
• lc_is_used(9)
• lc_del(9)
• lc_get(9)
• lc_try_get(9)
• lc_committed(9)
• lc_put(9)
• lc_element_by_index(9)
• lc_seq_dump_details(9)

---

okay that's the whole page, you ate that 💅 this came to you from ./lib, dated October 2026, and it's filed under lc_get_cumulative(9) — iconic, no notes 🎀🦋✨