RE: [PATCH] drm/xe: Use write-back caching mode for system memory on DGFX

2024-07-04 Thread Mrozek, Michal
The caching mode for buffer objects with VRAM as a possible placement was forced to write-combined, regardless of placement. However, write-combined system memory is expensive to allocate and even though it is pooled, the pool is expensive to shrink, since it involves global CPU TLB flushes. M

Re: [PATCH] drm/xe: Use write-back caching mode for system memory on DGFX

2024-07-02 Thread Rodrigo Vivi
On Wed, Jun 19, 2024 at 06:39:04PM +0200, Thomas Hellström wrote: > The caching mode for buffer objects with VRAM as a possible > placement was forced to write-combined, regardless of placement. > > However, write-combined system memory is expensive to allocate and > even though it is pooled, the

Re: [PATCH] drm/xe: Use write-back caching mode for system memory on DGFX

2024-07-02 Thread Souza, Jose
On Wed, 2024-06-19 at 18:39 +0200, Thomas Hellström wrote: > The caching mode for buffer objects with VRAM as a possible > placement was forced to write-combined, regardless of placement. > > However, write-combined system memory is expensive to allocate and > even though it is pooled, the pool is

Re: [PATCH] drm/xe: Use write-back caching mode for system memory on DGFX

2024-06-24 Thread Matt Roper
On Wed, Jun 19, 2024 at 06:39:04PM +0200, Thomas Hellström wrote: > The caching mode for buffer objects with VRAM as a possible > placement was forced to write-combined, regardless of placement. > > However, write-combined system memory is expensive to allocate and > even though it is pooled, the

Re: [PATCH] drm/xe: Use write-back caching mode for system memory on DGFX

2024-06-20 Thread Matthew Auld
On 19/06/2024 17:39, Thomas Hellström wrote: The caching mode for buffer objects with VRAM as a possible placement was forced to write-combined, regardless of placement. However, write-combined system memory is expensive to allocate and even though it is pooled, the pool is expensive to shrink,