The trick of course is to ensure that the exposed server state is valid at all times.
If "valid at all times" is interpreted literally (i.e. at any give time), this is not possible.
- A `desktop_shm_t` block is supposed to be arbitrarily large. - We cannot perform atomic operations on an arbitrarily large block of memory (exceeding e.g., 128 bits).
Therefore, we cannot perform atomic operations on a `desktop_shm_t` block.
Even if we get rid of nested updates, we need at least 1 bit of "dirty" state in `SEQUENCE_MASK`.