Deep within the imperial observatory east of Jiankang stood a water clock tower rising thirty cubits above the misty terrace.

Fed by cold springs trickling down tiered bronze basins, the clock’s floats lifted their marked arrows inch by inch against the dawn. At the center of the upper pavilion hung a nine-foot mica-powder screen. There, the Master Astrologer held his calculating rods, rapidly inscribing four delicate figures at the center of the scroll: the Right Ascension, Declination, Clepsydra Notch, and Terrestrial Bearing of the ruling constellations.

Below the terrace sat dozens of scribe-monks clad in white linen. Every half-quarter hour, envoys from the Imperial Hall, the Inner Palace Bell Registry, and the Bureau of Astronomers would arrive in haste to transcribe the four numbers and synchronize the realm’s reckoning of time.

In earlier reigns, the observatory was governed by the Bell-and-Bolt Protocol.

Whenever the Master Astrologer took up his red brush to amend the scroll, he would strike a bronze bell and drop a heavy bronze bolt across the screen’s wooden frame. The moment the bell chimed, every scribe below—even those midway through a single stroke—had to arrest their brush mid-air, bowing behind the barrier in anxious silence. Only after the astrologer completed his arithmetic, lifted the heavy bronze bolt, and struck a jade chime could the crowd of scribes surge forward to claim their transcriptions.

Yet the spring water surged without pause, and the heavenly bodies never ceased their orbits. The master’s numbers shifted slightly every few breaths.

A thousand times a day the heavy bolt clattered down. Each drop erected an invisible fortress across the hall. Couriers from the palace formed long, agitated queues down the stone stairs while scribes shuffled their sandals in place. When a calculation proved complex and the astrologer paused in contemplation, the bolt remained fast for long minutes, plunging the entire terrace into agonizing stagnation. When the bolt finally rose, dozens of scribes shoved against one another, blocking each other’s view and snapping bamboo brushes in their haste—delaying the morning chimes of the Great Throne Hall.

A new Master Astrologer took office. Seeking relief, he dismantled the bronze bolt entirely, swinging to the opposite extreme: “No bolts, no locks; transcribe as you please.”

The disaster that followed was swifter still. One midnight, the master revised the Ascension and the Clepsydra Notch, but before his brush could touch the Declination and the Terrestrial Bearing, an overeager palace page swept in and copied the numbers down. This half-baked, fractured ledger was carried straight to the throne hall. Relying on it, the bell-ringers tolled dawn bells in the pitch black of night, sending civilian and military ministers scurrying across frost-covered flagstones in complete disarray.

In the depths of that winter, the Grand Director of the Bureau himself visited the terrace. He brought neither heavy bolts nor decrees banning brushwork. Instead, atop the mica screen he suspended a small vermillion lacquer plaque, establishing three deceptively simple ordinances:

First: Evens signify stillness; odds announce change. The vermillion plaque bore a single black number, initialized to zero. Whenever the Master Astrologer prepared to alter a figure, he barred no one; he merely flipped the plaque by one notch, advancing the number to an odd value (one, three, five…). Once all four calculations were complete, he set down his brush and flipped the plaque once more, advancing it to an even number (two, four, six…).

Second: Read at will; verify the count twice. The white-robed scribes below waited for no bells and sought no permission. They arrived and transcribed at will. But before putting brush to paper, each had to raise his eyes and memorize the number on the plaque. If the count was odd, he knew the master’s brush was active and the figures in flux; he stepped back and waited a breath. If the count was even, he flew his brush across his handheld slip, capturing all four figures in haste. Upon finishing, he raised his eyes once more to re-examine the plaque.

Third: A match seals the ledger; a divergence damns the ink. If the plaque count upon completion matched the initial count to the digit, the scribe knew with mathematical certainty: during the fleeting span of his transcription, the master had never touched the plaque. The four numbers recorded were a pure, untorn, consistent snapshot. Conversely, if the number had changed—or shifted to an odd digit—it proved the writer had intervened mid-stroke. The scribe uttered no protest, shredded the tainted parchment without remorse, breathed, and began the reading anew.

The moment the ordinance took effect, the spirit of the observatory was reborn.

Dozens of white-clad scribes flowed through the pavilion like drifting mist. For ninety-nine percent of the day, the master was deep in contemplation, and the plaque remained motionless on an even digit. Scribes darted in, glanced up, flew their brushes, glanced again, and vanished down the terrace in the span of a single breath—with zero contention, zero waiting, and zero friction.

Even during the rare moments when the master updated the scroll, only the two or three scribes caught in mid-stroke had to discard a sheet and retry. The master himself never suffered hesitation from the press of crowds below; his brush danced across the silk with untroubled priority, completely oblivious to whether one scribe or ten thousand watched his strokes.

From that winter on, the water clocks of Jiankang struck with unblemished precision, and the stars moved across the heavens in flawless cadence.

—By now you have probably recognized the mechanism: the towering water clock and its four constantly shifting figures represent small, frequently queried core data structures in modern operating systems (such as jiffies_64, kernel timers, and network routing state in Linux); the calculating master and the flowing scribes represent concurrent writer and reader threads; the old “Bell-and-Bolt” that froze the court depicts the catastrophic bus contention and reader starvation of traditional Read-Write Spinlocks (rwlocks); and the tiny vermillion plaque flipping between odd and even is one of the most elegant, wait-free concurrency primitives in systems engineering—the Sequential Lock (SeqLock).

What it is

A Sequential Lock (commonly abbreviated as SeqLock) is a specialized synchronization mechanism introduced in the Linux 2.6 kernel, designed specifically for scenarios with very frequent readers, rare writers, and small, compact data structures.

While traditional read-write spinlocks (rwlocks) permit multiple concurrent readers, each reader must execute an atomic instruction (such as lock cmpxchg on x86) to update an internal reader counter. When dozens or hundreds of CPU cores read a single hot memory location simultaneously (such as the system wall clock or routing tables), these atomic writes force cache-coherence protocols to broadcast invalidation storms across inter-socket buses. The resulting cache line bouncing devastates read scalability, while a continuous stream of readers can starve the writer indefinitely.

SeqLock breaks this bottleneck by replacing shared locking with Optimistic Concurrency Control (OCC) driven by a sequence counter:

1. The Sequence Counter and Parity Invariant:
   • The lock maintains a single integer variable, sequence, initialized to 0 (an even number).
   • The Writer Protocol (Exclusive Mutation): Before entering its critical section, a writer acquires a standard spinlock (serializing against other writers) and increments sequence by 1, making it odd. This broadcasts to the hardware: “A write is underway; data is temporarily inconsistent!” Once the payload update completes, the writer increments sequence again to an even number and unlocks the spinlock. The writer enjoys absolute, unhindered priority.
   • The Reader Protocol (Lockless Optimistic Polling): Readers acquire no locks and execute zero atomic bus instructions. A reader simply samples sequence before reading:
     • If the value is odd, the reader spins briefly until the writer finishes and the value becomes even.
     • Once an even value seq1 is observed, the reader reads the payload data directly (guarded by memory barriers to preserve load ordering).
     • Upon finishing the read, the reader samples the sequence counter a second time, obtaining seq2.
     • The Consistency Check: If seq1 == seq2 (and remained even), the reader is guaranteed that no writer touched the data during the read. The captured snapshot is atomic and coherent.
     • If seq1 != seq2 (or was odd), a writer intervened mid-read, causing a torn read. The reader simply discards the torn payload and loops back to retry.

Why it matters

The SeqLock represents an indispensable engineering milestone in modern high-performance kernel design:

1. Zero Bus Contention on the Read Path (Wait-Free Scalability): Readers perform strictly read-only loads on the sequence counter and the payload. No cache line transitions to the Modified state, meaning the cache line can remain replicated in the Shared state across hundreds of cores indefinitely. Read scalability scales linearly with core counts, approaching the theoretical hardware limit.

2. Absolute Writer Priority Without Starvation: In traditional mutual exclusion, a writer can be stalled by slow readers or dense reader storms. In a SeqLock, the writer never yields to readers. It flips the counter, updates memory, and exits. For time-critical paths like operating system timer interrupts (timer IRQs) and high-resolution wall-clock updates (gettimeofday), this deterministic, low-latency execution is crucial.

3. Minimal Memory Overhead for Plain Old Data (POD): Unlike RCU (Read-Copy-Update), which relies on pointer indirection, dynamic allocations, and deferred grace periods for reclamation, a SeqLock operates directly on contiguous, flat data structures (POD structs). With merely an 8-byte integer counter and two memory barriers, it compresses synchronization overhead for small data down to nanoseconds.

Metaphor mapping

• The towering water clock and its four shifting figures → Small, contiguous kernel data structures updated periodically (e.g., Linux xtime / jiffies_64)
• The Master Astrologer updating the mica screen → The exclusive kernel writer thread or timer interrupt (Writer Thread)
• The endless stream of white-robed scribe-monks → Hundreds of CPU cores issuing concurrent read requests (Reader Threads)
• The old “Bell-and-Bolt” halting the hall → Heavy bus contention, cache line bouncing, and reader queuing under classic read-write locks (rwlock contention)
• The vermillion plaque and its inscribed number → The sequence counter inside the SeqLock (Sequence Counter)
• The master incrementing by one to an odd number before writing and returning to even upon finish → The writer toggling parity to advertise active mutation (Writer Sequence Odd/Even Transition)
• Scribes pausing upon seeing an odd number → Readers detecting an in-progress write and spinning until completion (Reader Spin Wait)
• Scribes memorizing the plaque before and after writing → Readers sampling seq1 and seq2 across the read window (Read Sequence Sampling)
• Identical plaque numbers sealing the ledger → Confirming seq1 == seq2 to ensure a consistent, non-torn snapshot (Sequence Match Validation)
• Tearing up paper and retrying upon a discrepancy → Discarding torn data and retrying the optimistic read loop (Optimistic Retry on Conflict)
• Scribes flowing freely while the master’s brush never halts → SeqLock’s zero-bus-contention read scalability and unblockable writer priority (Zero Cache Contention & Writer Priority)