Re: why are some atomic_t's not volatile, while most are?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Chris Snook wrote:

If your architecture doesn't support SMP, the volatile keyword doesn't do anything except add a useless memory fetch.

I was under the impression that there were other cases as well (interrupt handlers, for instance) where the value could be modified "behind the back" of the current code.

It seems like this would fall more into the case of the arch providing guarantees when using locked/atomic access rather than anything SMP-related, no?.

Chris
-
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]
  Powered by Linux