On Fri, Aug 29, 2014 at 12:18:45PM +0100, Chris Wilson wrote: > What I've done in the past is kept a global pool of used pages to avoid > clflushing fresh allocations in the kernel. That runs afoul of the ABI > that we need to scrub new bo. With a create2 we could specify a pool to > use that would be filp private and so have no greater information leak > than the current reuse. Probably will still be frowned upon, but a fun > idea to pursue... I think a per-filp page cache would actually be fairly sane. Presuming the added complexity can be justified with benchmarks ofc. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
