Messages in this thread | | | Date | Thu, 05 Jun 2014 18:44:37 -0400 | From | Pranith Kumar <> | Subject | regarding use of various cmpxchg* API |
| |
Hi Peter, Ingo,
I see that in the drivers there are the following types of cmpxchg API:
__cmpxchg64() atomic_cmpxchg() atomic64_cmpxchg() cmpxchg() atomic_long_cmpxchg() cmpxchg_local() local_cmpxchg()(in kernel/events/ring_buffer.c) this_cpu_cmpxchg()
Since cmpxchg() internally handles the width, do you think it makes sense to replace the above uses of cmpxchg with the document API (cmpxchg, atomic_cmpxchg, cmpxchg_local)?
I am willing to do this and wanted to know if it something you think is worth pursuing.
Regards, Pranith
| |