> To answer Linda's original question, whether it's necessary to use a lock
> is very much dependent on the operation you're performing. It's safe to
> assume there's an arbitrarily long delay before your write appears to
> another processor, but we're also currently assuming that all writes show
> up in the order they were performed.
--- Arbitrarily long...no upward bound? A second, minute, hour, day? Something doesn't seem right about that.You say we are 'assuming' writes show up in the order performed, that implies it may not be true? It seems the speculative read cache would only stay around for some fixed, finite, and small time -- unless the processor is halted. I can see getting the wrong value for the variable on 1 read, but after performing a system call another read shouldn't still fetch a stale value. Could it? -l
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jul 23 2000 - 21:00:15 EST