locking: Percpu-rwsem rewrite
Status from this message: The following commit has been merged into the locking/core branch of tip:
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | locking/percpu-rwsem, lockdep: Make percpu-rwsem use its own lockdep_mapinclude/ kernel/ kernel/ +2 more | +37 | 0 replies | |
| 2/7 | locking/percpu-rwsem: Convert to boolinclude/ kernel/ | +7 | 0 replies | |
| 3/7 | locking/percpu-rwsem: Move __this_cpu_inc() into the slowpathinclude/ kernel/ | +8 | 0 replies | |
| 4/7 | locking/percpu-rwsem: Extract __percpu_down_read_trylock()kernel/ | +13 | 0 replies | |
| 5/7 | locking/percpu-rwsem: Remove the embedded rwseminclude/ include/ include/ +3 more | +123 | 8 replies | |
| 5/7 | locking/percpu-rwsem: Remove the embedded rwseminclude/ include/ kernel/ +2 more | +123 | 0 replies | |
| 6/7 | locking/percpu-rwsem: Fold __percpu_up_read()include/ kernel/ kernel/ | +16 | 0 replies | |
| 7/7 | locking/percpu-rwsem: Add might_sleep() for writer lockingkernel/ | +1 | 0 replies |
Reviews trailers per patch
2 of 8 patches have a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Juri Lelli | Waiman Long | Davidlohr Bueso | Will Deacon | Christoph Hellwig |
|---|---|---|---|---|---|
| Series | T-b | A-b | R-b | A-b | |
| 1/7 | T-b | ||||
| 2/7 | T-b | ||||
| 3/7 | T-b | ||||
| 4/7 | T-b | ||||
| 5/7 | T-b T-b | A-b | R-b | A-b | Requested-by |
| 5/7 | T-b T-b | A-b | R-b | A-b | Requested-by |
| 6/7 | |||||
| 7/7 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 5 reviewers.
Cover letter [PATCH -v2 0/7] locking: Percpu-rwsem rewrite
Hi all,
This is the long awaited report of the percpu-rwsem rework (sorry Juri).
IIRC (I really have trouble keeping up momentum on this series) I've addressed all previous comments by Oleg and Davidlohr and Waiman and hope we can stick this in tip/locking/core for inclusion in the next merge.
It has been cooked (thoroughly) in PREEMPT_RT, and not found wanting.
Any objections to me stuffing it in so we can all forget about it properly?