Re: [PATCH 2/2] drm/amdgpu: Optimize mutex usage (v2)

2017-06-17 Thread Christian König
Am 17.06.2017 um 00:00 schrieb axie: On 2017-06-16 01:48 PM, Christian König wrote: Am 16.06.2017 um 07:03 schrieb Alex Xie: Use rw_semaphore instead of mutex for bo_lists. In original function amdgpu_bo_list_get, the waiting for result->lock can be quite long while mutex bo_list_lock was

Re: [PATCH 2/2] drm/amdgpu: Optimize mutex usage (v2)

2017-06-16 Thread axie
On 2017-06-16 01:48 PM, Christian König wrote: Am 16.06.2017 um 07:03 schrieb Alex Xie: Use rw_semaphore instead of mutex for bo_lists. In original function amdgpu_bo_list_get, the waiting for result->lock can be quite long while mutex bo_list_lock was holding. It can make other tasks

Re: [PATCH 2/2] drm/amdgpu: Optimize mutex usage (v2)

2017-06-16 Thread Christian König
Am 16.06.2017 um 07:03 schrieb Alex Xie: Use rw_semaphore instead of mutex for bo_lists. In original function amdgpu_bo_list_get, the waiting for result->lock can be quite long while mutex bo_list_lock was holding. It can make other tasks waiting for bo_list_lock for long period too. Change

Re: [PATCH 2/2] drm/amdgpu: Optimize mutex usage (v2)

2017-06-15 Thread Michel Dänzer
On 16/06/17 02:03 PM, Alex Xie wrote: > Use rw_semaphore instead of mutex for bo_lists. > > In original function amdgpu_bo_list_get, the waiting > for result->lock can be quite long while mutex > bo_list_lock was holding. It can make other tasks > waiting for bo_list_lock for long period too. >

[PATCH 2/2] drm/amdgpu: Optimize mutex usage (v2)

2017-06-15 Thread Alex Xie
Use rw_semaphore instead of mutex for bo_lists. In original function amdgpu_bo_list_get, the waiting for result->lock can be quite long while mutex bo_list_lock was holding. It can make other tasks waiting for bo_list_lock for long period too. Change bo_list_lock to rw_semaphore can avoid most of