kref: inline and barriers
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 37 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | kref: Inline all functionsinclude/ lib/ lib/ | +75 | 8 replies | |
| 2/3 | kref: Implement kref_put in terms of kref_subinclude/ | +10 | 0 replies | |
| 3/3 | kref: Remove the memory barriersinclude/ | +0 | 29 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] kref: inline and barriers
Quoted 1 line
From time to time people on #kernelnewbies ask what the difference is between
kref and using atomic_t yourself. And I keep having to tell them that kref is the slow and weird option.
These patches try and cure some of that, it inlines all functions and removes the superfluous memory barriers that are there for no good reason at all.