drm/ttm: Get rid of a number of atomic read-modify-write ops v2
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | drm: Make hashtab rcu-safedrivers/ | +7 | 0 replies | |
| 2/4 | kref: Implement kref_get_unless_zero v2include/ | +21 | 0 replies | |
| 3/4 | drm/ttm, drm/vmwgfx: Use RCU locking for object lookups v2drivers/ drivers/ include/ | +19 | 0 replies | |
| 4/4 | drm/ttm: Optimize reservation slightlydrivers/ | +2 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] drm/ttm: Get rid of a number of atomic read-modify-write ops v2
A patch series for next that removes a substantial number of read-modify-write operations from TTM command submission, in particular if TTM objects are used to export objects to user-space. The only per-object atomic r-m-w operations left during a typical execbuf call should be refcount up and down.
v2: Formatting fixes.
In-Reply-To:
Quoted 1 line
From Thomas Hellstrom <[email protected]> # This line is ignored.
From: Thomas Hellstrom <[email protected]>
Subject:
In-Reply-To: