find_wl_entry(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay so bestie, this is find_wl_entry(9) from the Kernel API Manual, and she is here to find the wear-leveling entry closest to a certain erase counter. no cap, that's the whole mission πŸ’…

πŸ¦‹ SYNOPSIS πŸ¦‹

struct ubi_wl_entry * find_wl_entry (struct ubi_device *ubi , struct rb_root *root , int diff , int pick_max );

πŸŽ€ ARGUMENTS πŸŽ€

  • ubi β€” the UBI device description object 🫢
  • root β€” the RB-tree where to look for πŸ‘€
  • diff β€” maximum possible difference from the smallest erase counter ✨
  • pick_max β€” pick PEB even its erase counter beyonds 'min_ec + diff' πŸ’€ (yes, β€œbeyonds,” we are keeping the original wording, don't come for me)

🌸 DESCRIPTION 🌸

She looks for a wear leveling entry whose erase counter is closest to min + diff, where min is the smallest erase counter. that's the vibe check, and she ate πŸ”₯

πŸ’œ SEE ALSO πŸ’œ

Kernel file ./drivers/mtd/ubi/wl.c β€” plus the whole squad: wl_tree_add(9), wl_entry_destroy(9), do_work(9), in_wl_tree(9), in_pq(9), prot_queue_add(9), find_mean_wl_entry(9), wl_get_wle(9), prot_queue_del(9), ubi_sync_erase(9), serve_prot_queue(9), __schedule_ubi_work(9), schedule_ubi_work(9), schedule_erase(9), do_sync_erase(9), wear_leveling_worker(9), ensure_wear_leveling(9), __erase_worker(9), ubi_wl_put_peb(9), ubi_wl_scrub_peb(9), ubi_wl_flush(9), ubi_bitflip_check(9), tree_destroy(9), ubi_thread(9), shutdown_work(9), erase_aeb(9), ubi_wl_init(9), protection_queue_destroy(9), ubi_wl_close(9), self_check_ec(9), self_check_in_wl_tree(9), self_check_in_pq(9), produce_free_peb(9), ubi_wl_get_peb(9). iconic list, honestly πŸ‘‘


source/version: ./drivers/mtd/ubi Β· date: October 2026 Β· page: find_wl_entry(9) β€” mwah, bye bestie πŸ’‹πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from