> > We really can't. We _only_ have load-and-zero. And it has to be 16-byte > > aligned. xchg() is just not something the CPU implements. > > The network code relies on the reader-xchg semantics David described in > several places. I guess the network code will just have to change for 2.5. read_xchg_val() can be a null macro for everyone else at least - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- [PATCH] move xchg/cmpxchg to atomic.h Grant Grundler
- Re: [PATCH] move xchg/cmpxchg to atomic.h David S. Miller
- Re: [PATCH] move xchg/cmpxchg to atomic.h Matthew Wilcox
- Re: [PATCH] move xchg/cmpxchg to atomic.h David S. Miller
- Re: [PATCH] move xchg/cmpxchg to atomic.h Roman Zippel
- Re: [PATCH] move xchg/cmpxchg to ato... Daniel Phillips
- Re: [PATCH] move xchg/cmpxchg to atomic.h Andi Kleen
- Re: [PATCH] move xchg/cmpxchg to atomic.h Alan Cox
- Re: [PATCH] move xchg/cmpxchg to ato... Linus Torvalds
- Re: [PATCH] move xchg/cmpxchg to atomic.h Grant Grundler