Messages in this thread | | | Date | Thu, 16 Aug 2007 11:48:23 -0700 (PDT) | From | Christoph Lameter <> | Subject | Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures |
| |
On Thu, 16 Aug 2007, Paul Mackerras wrote:
> > It seems that there could be a lot of places where atomic_t is used in > a non-atomic fashion, and that those uses are either buggy, or there > is some lock held at the time which guarantees that other CPUs aren't > changing the value. In both cases there is no point in using > atomic_t; we might as well just use an ordinary int.
The point of atomic_t is to do atomic *changes* to the variable. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |