Skip to content

drm/ttm: Get rid of a number of atomic read-modify-write ops v2

Thomas Hellstrom dri-devel lkml 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4drm: Make hashtab rcu-safedrivers/gpu/drm/drm_hashtab.c+7 -110 replies
2/4kref: Implement kref_get_unless_zero v2include/linux/kref.h+21 -00 replies
3/4drm/ttm, drm/vmwgfx: Use RCU locking for object lookups v2drivers/gpu/drm/ttm/ttm_object.c drivers/gpu/drm/vmwgfx/vmwgfx_resource.c include/drm/ttm/ttm_object.h+19 -230 replies
4/4drm/ttm: Optimize reservation slightlydrivers/gpu/drm/ttm/ttm_bo.c+2 -10 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

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: