ip_vs_rht_walk_bucket_rcu(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ip_vs_rht_walk_bucket_rcu(9) — bestie's guide to the Kernel API Manual

okay so gather round, this is the page for ip_vs_rht_walk_bucket_rcu(9), straight out of the Kernel API Manual, and honestly? it's giving "tiny function, big responsibilities" ✨

🌸 NAME 🌸

ip_vs_rht_walk_bucket_rcu — walk a bucket while holding the RCU read lock 🫶

✨ SYNOPSIS ✨

ip_vs_rht_walk_bucket_rcu (t , bucket , head );

yes bestie, that's the whole call, spaces and all, no cap 💅

🎀 ARGUMENTS 🎀

  • t — the current table, and it's literally a struct ip_vs_rht *var 👑
  • bucket — the index of the current bucket or the hash key, whichever vibe you're on 🔥
  • head — the bucket address, and it's used as the cursor — it's a struct hlist_bl_head *var in case you were wondering 🦋

💖 DESCRIPTION 💖

okay so here's the tea: you can totally use this while other people are out here adding, deleting, and moving entries around. it's built for that chaos, slay 💀

but — and this is the important part — it's not suitable if duplicates are not desired. like, if you need everything to be unique and pristine, this is not the function for you, sorry not sorry 🙈

now, here's the possible cases for a reader that uses cond_resched_rcu in the loop, and yes there are exactly two, we don't do extras here:

  • new table can not be installed — no need to repeat, you're done, go touch grass 🌈
  • new table can be installed — so check and repeat if a new table is installed, and this one's needed for !PREEMPT_RCU ⭐
lowkey important, so like... read it twice bestie 🧚

🦋 SEE ALSO 🦋

check out the Kernel file ./include/net/ip_vs.h — that's the spot 🍓

and then the whole friend group of related functions, in this exact order, periodt:

and that's the whole page, mwah 💋

cute little sign-off: this one lives in ./include/net, it's dated October 2026, and the page is ip_vs_rht_walk_bucket_rcu(9) — ily, go walk some buckets responsibly 💜

📦 where this page comes from