ring-buffer: less locking and only disable preemption
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 12 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | ring-buffer: move page indexes into page headerskernel/ | +41 | 0 replies | |
| 2/3 | ring-buffer: make reentrantkernel/ | +373 | 0 replies | |
| 3/3 | ftrace: make some tracers reentrantkernel/ kernel/ | +4 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] ring-buffer: less locking and only disable preemption
Ingo,
These patches need to be put through the ringer. Could you add them to your ring-buffer branch, so we can test them out before putting them into your master branch.
The following patches bring the ring buffer closer to a lockless solution. They move the locking only to the actual moving the tail/write pointer from one page to the next. Interrupts are now enabled during most of the writes.
A lot of the locking protection is still within the ftrace infrastructure. The last patch takes some of that away.
The function tracer cannot be reentrant just due to the nature that it traces everything, and can cause recursion issues.
-- Steve