RFC Remove local_t
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 RFC Latest3 patches 1 replyIn review
- v1 RFC4 patches 19 repliesSuperseded
Changes in v2 from the cover letter
- Preserve local.h
- Add a rationale why the remaining functions are useful and how they differ from this_cpu_xx.
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | Remove unused local.h functionsarch/ arch/ arch/ +3 more | +3 | 0 replies | |
| 2/3 | Remove local_t type from tree.arch/ arch/ arch/ +5 more | +141 | 1 reply | |
| 3/3 | Eliminate local_cmpxchgarch/ arch/ arch/ +4 more | +3 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [RFC local_t removal V2 0/3] Remove local_t
Current -next has only the trace subsystem left as a user of local_t
Tracing uses local_t for per cpu safe atomic operations in the form of cmpxchg and additions.
This patchset removes unused function in local.h and then genericizes local.h by removing local_t. This results in a very small set of functions.
"long" is used for now instead of local_t. With some additional work it would be possible to pass arbitrary types to local_xx() function like cmpxchg_local() and the this_cpu_xx() functions. Maybe a more flexible way of handling local_xx() would allow the use of these functions in other kernel subsystems.
Still RFC state. Lots of stuff todo. Compiles on my box.
V1->V2
- Preserve local.h
- Add a rationale why the remaining functions are useful and how they differ from this_cpu_xx.