* Paul E. McKenney <[email protected]> wrote:
> Now, it is true that CPU#2 might record a quiescent state during this
> time, but this will have no effect because -all- CPUs must pass
> through a quiescent state before any callbacks will be invoked. Since
> CPU#1 is refusing to record a quiescent state, grace periods will be
> blocked for the full extent of task 1's RCU read-side critical
> section.
ok, great. So besides the barriers issue (and the long grace period time
issue), the current design is quite ok. And i think your original flip
pointers suggestion can be used to force synchronization.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
