Messages in this thread | | | Date | Thu, 27 Jan 2005 18:14:33 -0800 | From | Paul Jackson <> | Subject | Re: [patch, 2.6.10-rc2] sched: fix ->nr_uninterruptible handling bugs |
| |
True - thanks - including the part about the cost of locking bugs.
My question was poorly phrased - the code speaks the answer to the real question I had:
$ grep define.atomic_ include/asm-ia64/atomic.h | head -2 #define atomic_read(v) ((v)->counter) #define atomic_set(v,i) (((v)->counter) = (i))
An atomic_read() of a one word counter on ia64 is just a load, and an atomic_set() is just a store. This is unlike the more difficult atomic_inc, atomic_dec, atomic_add, atomic_mutilate, ... calls that require something fancier, and I presume more painful for that CPUs innards.
Good. Thanks.
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.650.933.1373, 1.925.600.0401 - 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/
| |