>this has been discussed already, but how much trouble should I expect
>(portability wise), if I replace the current fifo with an non-locking fifo
>using asm/atomic.h? In other words, is it worth the trouble to keep both,
>and write autoconf macros that check for asm/atomic.h...? And the natural
>next question, has someone already done this? :)

because of problems with LinuxPPC and kernel 2.2, there should be a
version of <pbd/atomic.h> in the next couple of days that will contain
the actual asm for atomic_t ops on most platforms. 

--p

Reply via email to