[PATCH 1/2] drm/amdgpu: guarantee bijective mapping of ring ids for LRU v3

2017-03-28 Thread Andres Rodriguez
Depending on usage patterns, the current LRU policy may create a non-injective mapping between userspace ring ids and kernel rings. This behaviour is undesired as apps that attempt to fill all HW blocks would be unable to reach some of them. This change forces the LRU policy to create bijective m

Re: [PATCH 1/2] drm/amdgpu: guarantee bijective mapping of ring ids for LRU

2017-03-28 Thread Nicolai Hähnle
On 28.03.2017 00:36, Andres Rodriguez wrote: Depending on usage patterns, the current LRU policy may create a non-injective mapping between userspace ring ids and kernel rings. This behaviour is undesired as apps that attempt to fill all HW blocks would be unable to reach some of them. This cha

Re: [PATCH 1/2] drm/amdgpu: guarantee bijective mapping of ring ids for LRU

2017-03-27 Thread Andres Rodriguez
Forgot to add v2: compressed ring_blacklist (nha) On 2017-03-27 06:36 PM, Andres Rodriguez wrote: Depending on usage patterns, the current LRU policy may create a non-injective mapping between userspace ring ids and kernel rings. This behaviour is undesired as apps that attempt to fill all HW

[PATCH 1/2] drm/amdgpu: guarantee bijective mapping of ring ids for LRU

2017-03-27 Thread Andres Rodriguez
Depending on usage patterns, the current LRU policy may create a non-injective mapping between userspace ring ids and kernel rings. This behaviour is undesired as apps that attempt to fill all HW blocks would be unable to reach some of them. This change forces the LRU policy to create bijective m

Re: [PATCH 1/2] drm/amdgpu: guarantee bijective mapping of ring ids for LRU

2017-03-27 Thread Andres Rodriguez
On 2017-03-23 08:02 AM, Nicolai Hähnle wrote: On 17.03.2017 19:52, Andres Rodriguez wrote: Depending on usage patterns, the current LRU policy may create a non-injective mapping between userspace ring ids and kernel rings. This behaviour is undesired as apps that attempt to fill all HW blocks

Re: [PATCH 1/2] drm/amdgpu: guarantee bijective mapping of ring ids for LRU

2017-03-23 Thread Nicolai Hähnle
On 17.03.2017 19:52, Andres Rodriguez wrote: Depending on usage patterns, the current LRU policy may create a non-injective mapping between userspace ring ids and kernel rings. This behaviour is undesired as apps that attempt to fill all HW blocks would be unable to reach some of them. This cha

[PATCH 1/2] drm/amdgpu: guarantee bijective mapping of ring ids for LRU

2017-03-17 Thread Andres Rodriguez
Depending on usage patterns, the current LRU policy may create a non-injective mapping between userspace ring ids and kernel rings. This behaviour is undesired as apps that attempt to fill all HW blocks would be unable to reach some of them. This change forces the LRU policy to create bijective m