This is not the current version of the class.

Lecture 21: RCU

Notes by Thomas Lively

Front matter

Problem set 4 is no longer stalled

See new test program, system call, etc.

Here's the paper

Remember the RW lock:

struct rwlock {
atomic<int> v_;

while (v_ >= 0 && cas(&v_, v, v+1)) {}
}

--v_;
}

... see last notes


Problems with RW lock:

• This one happens to starve writers
• All threads are performing expensive atomic operations on the same location
• Can we not?

int i; // global

int tmp = i; // load i


This works in practice (on x86) but is not allowed according to the rules!!! And the rules say "Violators may be prosecuted" (rules, page ii).

Let's follow the rules this time:

std::atomic<int> i; // global
int tmp = i.load(std::memory_order_relaxed); // AFAPBNUB


(AFAPBNUB = As far as possible but no undefined behavior)

This follows the rules, but only for smallish values. What do we do in the following situation?

struct largestruct {
char[10000] c;
}

spinlcok l_lock;
largestruct *l; // global
std::atomic<largestruct*> l;

// write
largestruct *n = allocate();
l_lock.lock();
ptr.store(n);
l_lock.unlock();
kfree(old);


Now we have a lock but at least we have consistent lock-free reads.

But we don't know when we can safely free the data!

Goal: Let's delay the free until readers are done (without a read lock). We can do this because freeing data:

• is important
• is time-insensitive
• has no effect on the calling thread

Let's consider an example syscall

case SYSCALL_BAD: {
x, y, z
if (x == 0) {
// calculate checksum ...
return checksum;
} else {
// write large struct
largestruct *n = ...;
memcpy(&n->c, y, z);
l.store(n);
}
...
}


We can have multiple threads reading and writing simultaneously. We want to know when an old snapshot is no longer visible to any readers.

Once a reader gets back to user mode it is impossible for it to be looking at the old snapshot or ever get another reference to it. So we just need to make sure every CPU has called cpu::schedule before we free the old object.

Interrupts can break the RCU guarantee. If an interrupt happens during an RCU critical section, and the interrupt causes the RCU-using task to be rescheduled, the RCU system can get confused and free something that is still referenced. So we have to disable interrupts or set a flag to disable preemption.