Re: [PATCH 7/9] drm/amdgpu: Throttle visible VRAM moves separately

2017-06-27 Thread Michel Dänzer
On 27/06/17 07:29 AM, John Brooks wrote: > On Mon, Jun 26, 2017 at 06:44:30PM +0900, Michel Dänzer wrote: >> On 24/06/17 02:39 AM, John Brooks wrote: >>> The BO move throttling code is designed to allow VRAM to fill quickly if it >>> is relatively empty. However, this does not take into account sit

Re: [PATCH 7/9] drm/amdgpu: Throttle visible VRAM moves separately

2017-06-26 Thread John Brooks
On Mon, Jun 26, 2017 at 06:44:30PM +0900, Michel Dänzer wrote: > On 24/06/17 02:39 AM, John Brooks wrote: > > The BO move throttling code is designed to allow VRAM to fill quickly if it > > is relatively empty. However, this does not take into account situations > > where the visible VRAM is smalle

Re: [PATCH 7/9] drm/amdgpu: Throttle visible VRAM moves separately

2017-06-26 Thread Michel Dänzer
On 24/06/17 02:39 AM, John Brooks wrote: > The BO move throttling code is designed to allow VRAM to fill quickly if it > is relatively empty. However, this does not take into account situations > where the visible VRAM is smaller than total VRAM, and total VRAM may not > be close to full but the vi

[PATCH 7/9] drm/amdgpu: Throttle visible VRAM moves separately

2017-06-23 Thread John Brooks
The BO move throttling code is designed to allow VRAM to fill quickly if it is relatively empty. However, this does not take into account situations where the visible VRAM is smaller than total VRAM, and total VRAM may not be close to full but the visible VRAM segment is under pressure. In such sit