lc_create(9)

💖 lc_create(9) 💖

okay bestie, welcome to the Kernel API Manual — we're talking about lc_create, and it's giving “let's get this cache tracker set up” energy. ✨

🌸 NAME 🌸

lc_create — prepares to track objects in an active set 🫶

🎀 SYNOPSIS 🎀

struct lru_cache * lc_create (const char *name , struct kmem_cache *cache , unsigned max_pending_changes , unsigned e_count , size_t e_size , size_t e_off );

💅 ARGUMENTS 💅

• name — a descriptive name, and literally only used in lc_seq_printf_stats and lc_seq_dump_details. It's the nickname, not the whole personality. 🎀
• cache — the cache root pointer. 🌱
• max_pending_changes — the maximum changes to accumulate until a transaction is required. Basically the “how much chaos before we need a commit moment” limit. 💀
• e_count — number of elements allowed to be active simultaneously. 👯‍♀️
• e_size — size of the tracked objects. 📏
• e_off — offset to the struct lc_element member in a tracked object. 📍

🦋 DESCRIPTION 🦋

Returns a pointer to a newly initialized struct lru_cache on success, or NULL on (allocation) failure. That's it, that's the vibe check: got a fresh cache pointer? slay. Got NULL? allocation said no. 😭

🔥 SEE ALSO 🔥

The kernel file is ./lib/lru_cache.c, and the rest of the squad is:

• 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_get_cumulative(9)
• lc_try_get(9)
• lc_committed(9)
• lc_put(9)
• lc_element_by_index(9)
• lc_seq_dump_details(9)

mwah 💋 — straight from ./lib, October 2026, and that's the lc_create(9) moment. 🫶