rcu_set_gpwrap_lag(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ rcu_set_gpwrap_lag ✨

Okay bestie, welcome to the kernel API manual for rcu_set_gpwrap_lag(9) β€” yes, that’s the whole vibe, and no, we are not skipping a single detail. 🫢


🌸 NAME 🌸

rcu_set_gpwrap_lag β€” set the RCU GP sequence overflow lag value. Lowkey iconic, highkey niche. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

void rcu_set_gpwrap_lag (unsigned long lag_gps );

That’s it. That’s the whole signature. Slay. ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • lag_gps β€” set the overflow lag to this many grace period worth of counters. It’s used by rcutorture to quickly force a gpwrap situation. And if lag_gps = 0, that means we reset it back to the boot-time value. Periodt. πŸ’–

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./kernel/rcu/tree.c β€” and literally all of these friends:


πŸ’€ Friendly reminder: lag_gps = 0 is not a β€œnothing” value, bestie β€” it resets the overflow lag back to the boot-time value. Do not play with it unless you know what you’re doing.

And that’s the page, bestie! This little piece of kernel lore lives in ./kernel/rcu, dates back to October 2026, and the manual page is literally called rcu_set_gpwrap_lag(9). Go forth and force a gpwrap situation responsibly. πŸŒˆπŸ’œ

πŸ“¦ where this page comes from