ip_vs_rht_walk_buckets_rcu(9)

💅 ip_vs_rht_walk_buckets_rcu(9) — Kernel API Manual bestie era ✨

okay so this is the Kernel API Manual page for ip_vs_rht_walk_buckets_rcu(9), and we are literally about to walk all the buckets under an RCU read lock together 🫶 no cap.

🌸 NAME 🌸

ip_vs_rht_walk_buckets_rcu — walk all buckets under RCU read lock. That's the whole assignment bestie: buckets, RCU read lock, walking 💅.

🦋 SYNOPSIS 🦋

ip_vs_rht_walk_buckets_rcu (table , head );

🎀 ARGUMENTS 🎀

• table — struct ip_vs_rht __rcu *table. That's the table getting walked, periodt.
• head — bucket address, used as cursor, struct hlist_bl_head *var. It's giving cursor energy ✨.

💖 DESCRIPTION 💖

okay so the tea ☕: this can be used while others add/delete/move entries. But bestie, it is not suitable if duplicates are not desired 🙈.

Possible cases for reader that uses cond_resched_rcu in the loop:

• new table can not be installed, no need to repeat
• new table can be installed => check and repeat if new table is installed, needed for !PREEMPT_RCU

🔥 SEE ALSO 🔥

The kernel file is ./include/net/ip_vs.h — go read it, iykyk 👑

• ip_vs_rht_for_each_table(9)
• ip_vs_rht_for_each_table_rcu(9)
• ip_vs_rht_for_each_bucket(9)
• ip_vs_rht_for_bucket_retry(9)
• DECLARE_IP_VS_RHT_WALK_BUCKETS_RCU(9)
• DECLARE_IP_VS_RHT_WALK_BUCKET_RCU(9)
• ip_vs_rht_walk_bucket_rcu(9)
• DECLARE_IP_VS_RHT_WALK_BUCKETS_SAFE_RCU(9)
• ip_vs_rht_walk_buckets_safe_rcu(9)
• DECLARE_IP_VS_RHT_WALK_BUCKETS(9)
• ip_vs_rht_walk_buckets(9)

mwah 💋 — source ./include/net, dated October 2026, and the page tag is ip_vs_rht_walk_buckets_rcu(9). slay 🫶✨