On Sat, 17 Sep 2011 20:55:49 +0200, Daniel Vetter <[email protected]> wrote: > Like for shmem_pwrite_slow. The only difference is that because we > read data, we can leave the fetched cachelines in the cpu: In the case > that the object isn't in the cpu read domain anymore, the clflush for > the next cpu read domain invalidation will simply drop these > cachelines. > > slow_shmem_bit17_copy is now ununsed, so kill it. > > With this patch tests/gem_mmap_gtt now actually works.
I have to ask the obvious question: does this have any impact on CPU pwrite performance? Bring on prefaulting ;-) -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
