find_or_make_vacancy(9)

🌸 NAME 🌸

find_or_make_vacancy — literally here to find an empty bucket. Welcome to the Kernel API Manual, bestie; this page is all about that vacancy-finding moment. 💖

✨ SYNOPSIS ✨

struct bucket * find_or_make_vacancy (struct int_map *map , struct bucket *neighborhood );

🎀 ARGUMENTS 🎀

• map — the int_map to search or modify. That's the map bestie, okay? 🗺️
• neighborhood — the first bucket in the neighborhood in which an empty bucket is needed for a new mapping. It's giving “starting point” energy. 🪣

💅 DESCRIPTION 💅

Okay so the whole vibe is: find an empty bucket in a specified neighborhood for a new mapping, or attempt to re-arrange mappings so there is such a bucket. That's the mission, no cap. ✨

This operation may fail (returning NULL) if an empty bucket is not available or could not be relocated to the neighborhood. So yeah, it can absolutely gag and return NULL — that's a real outcome, not a drill. 😭

🦋 RETURN 🦋

a pointer to an empty bucket in the desired neighborhood, or NULL if a vacancy could not be found or arranged. That's the whole return situation, bestie — pointer when it slays, NULL when the vacancy arrangement says “not today.” 💀

🌈 SEE ALSO 🌈

For the full lore, peek at the Kernel file ./drivers/md/dm-vdo/int-map.c and this iconic lineup: Introduction(9), struct bucket(9), struct int_map(9), mix(9), hash_key(9), allocate_buckets(9), vdo_int_map_create(9), vdo_int_map_free(9), vdo_int_map_size(9), dereference_hop(9), insert_in_hop_list(9), select_bucket(9), search_hop_list(9), vdo_int_map_get(9), resize_buckets(9), find_empty_bucket(9), move_empty_bucket(9), update_mapping(9), vdo_int_map_put(9), and vdo_int_map_remove(9). Obsessed with this friend group, fr fr. 🫶

Source/version/date check, bestie: this page lives in ./drivers/md/dm-vdo, dates to October 2026, and signs off as find_or_make_vacancy(9). Periodt. 💅✨