702adba224
The bo lock used only to protect the bo sync object members, and since it is a per bo lock, fencing a buffer list will see a lot of locks and unlocks. Replace it with a per-device lock that protects the sync object members on *all* bos. Reading and setting these members will always be very quick, so the risc of heavy lock contention is microscopic. Note that waiting for sync objects will always take place outside of this lock. The bo device fence lock will eventually be replaced with a seqlock / rcu mechanism so we can determine that a bo is idle under a rcu / read seqlock. However this change will allow us to batch fencing and unreserving of buffers with a minimal amount of locking. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Jerome Glisse <j.glisse@gmail.com> Signed-off-by: Dave Airlie <airlied@redhat.com> |
||
|---|---|---|
| .. | ||
| Makefile | ||
| ttm_agp_backend.c | ||
| ttm_bo_manager.c | ||
| ttm_bo_util.c | ||
| ttm_bo_vm.c | ||
| ttm_bo.c | ||
| ttm_execbuf_util.c | ||
| ttm_lock.c | ||
| ttm_memory.c | ||
| ttm_module.c | ||
| ttm_object.c | ||
| ttm_page_alloc.c | ||
| ttm_tt.c | ||