Messages in this thread | | | Date | Tue, 9 Jan 2007 23:41:00 +0100 | From | Pavel Machek <> | Subject | Re: [PATCH] local_t : Documentation |
| |
Hi!
> > > These patches extend and standardise local_t operations on each architectures, > > > allowing a rich set of atomic operations to be done on per-cpu data with > > > minimal performance impact. On some architectures, there seems to be no > > > difference between the SMP and UP operation (same memory barriers, same > > > LOCking), local.h simply includes asm-generic/local.h, which removes duplicated > > > code. > > > > Could you provide some Documentation/? Knowing when local_t can be > > used is kind-of important. > > Hi Pavel, > > Thanks for this appropriate comment. I totally agree that there is a need for > documentation about how local_t variables should be used. Here is the patch > that adds Documentation/local_ops.txt. Comments are welcome.
AFAICT this fails to mention... Is local_t as big as int? As big as long? Or perhaps smaller because high bits may be needed for locking?
Pavel
-- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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/
| |