[PATCH] drm/ttm: do not try to preserve caching state

2012-11-28 Thread Thomas Hellstrom
On 11/28/2012 09:09 PM, Jerome Glisse wrote: > On Wed, Nov 28, 2012 at 10:05 AM, wrote: >> From: Jerome Glisse >> >> It make no sense to preserve caching state especialy when >> moving from vram to system. It burden the page allocator to >> match the vram caching (often WC) which just burn CPU c

[PATCH] drm/ttm: do not try to preserve caching state

2012-11-28 Thread Jerome Glisse
On Wed, Nov 28, 2012 at 6:13 PM, Jerome Glisse wrote: > On Wed, Nov 28, 2012 at 5:18 PM, Thomas Hellstrom > wrote: >> On 11/28/2012 09:09 PM, Jerome Glisse wrote: >>> >>> On Wed, Nov 28, 2012 at 10:05 AM, wrote: From: Jerome Glisse It make no sense to preserve caching stat

[PATCH] drm/ttm: do not try to preserve caching state

2012-11-28 Thread Jerome Glisse
On Wed, Nov 28, 2012 at 5:18 PM, Thomas Hellstrom wrote: > On 11/28/2012 09:09 PM, Jerome Glisse wrote: >> >> On Wed, Nov 28, 2012 at 10:05 AM, wrote: >>> >>> From: Jerome Glisse >>> >>> It make no sense to preserve caching state especialy when >>> moving from vram to system. It burden the pag

Re: [PATCH] drm/ttm: do not try to preserve caching state

2012-11-28 Thread Jerome Glisse
On Wed, Nov 28, 2012 at 6:13 PM, Jerome Glisse wrote: > On Wed, Nov 28, 2012 at 5:18 PM, Thomas Hellstrom wrote: >> On 11/28/2012 09:09 PM, Jerome Glisse wrote: >>> >>> On Wed, Nov 28, 2012 at 10:05 AM, wrote: From: Jerome Glisse It make no sense to preserve caching state e

Re: [PATCH] drm/ttm: do not try to preserve caching state

2012-11-28 Thread Jerome Glisse
On Wed, Nov 28, 2012 at 5:18 PM, Thomas Hellstrom wrote: > On 11/28/2012 09:09 PM, Jerome Glisse wrote: >> >> On Wed, Nov 28, 2012 at 10:05 AM, wrote: >>> >>> From: Jerome Glisse >>> >>> It make no sense to preserve caching state especialy when >>> moving from vram to system. It burden the page

[PATCH] drm/ttm: do not try to preserve caching state

2012-11-28 Thread Jerome Glisse
On Wed, Nov 28, 2012 at 10:05 AM, wrote: > From: Jerome Glisse > > It make no sense to preserve caching state especialy when > moving from vram to system. It burden the page allocator to > match the vram caching (often WC) which just burn CPU cycle > for no good reasons. > > Signed-off-by: Jerom

Re: [PATCH] drm/ttm: do not try to preserve caching state

2012-11-28 Thread Thomas Hellstrom
On 11/28/2012 09:09 PM, Jerome Glisse wrote: On Wed, Nov 28, 2012 at 10:05 AM, wrote: From: Jerome Glisse It make no sense to preserve caching state especialy when moving from vram to system. It burden the page allocator to match the vram caching (often WC) which just burn CPU cycle for no g

Re: [PATCH] drm/ttm: do not try to preserve caching state

2012-11-28 Thread Jerome Glisse
On Wed, Nov 28, 2012 at 10:05 AM, wrote: > From: Jerome Glisse > > It make no sense to preserve caching state especialy when > moving from vram to system. It burden the page allocator to > match the vram caching (often WC) which just burn CPU cycle > for no good reasons. > > Signed-off-by: Jerom

[PATCH] drm/ttm: do not try to preserve caching state

2012-11-28 Thread j . glisse
From: Jerome Glisse It make no sense to preserve caching state especialy when moving from vram to system. It burden the page allocator to match the vram caching (often WC) which just burn CPU cycle for no good reasons. Signed-off-by: Jerome Glisse --- drivers/gpu/drm/ttm/ttm_bo.c | 15 +++-

[PATCH] drm/ttm: do not try to preserve caching state

2012-11-28 Thread j.gli...@gmail.com
From: Jerome Glisse It make no sense to preserve caching state especialy when moving from vram to system. It burden the page allocator to match the vram caching (often WC) which just burn CPU cycle for no good reasons. Signed-off-by: Jerome Glisse --- drivers/gpu/drm/ttm/ttm_bo.c | 15 +++-