On Fri, Mar 17, 2017 at 10:52:16AM +0200, Joonas Lahtinen wrote: > On to, 2017-03-16 at 13:19 +0000, Chris Wilson wrote: > > Since obj->active_count is only updated upon retirement, if we see an > > active object in the batch pool, double check that is still active > > before deciding to allocate a new object. > > > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > > Any specific testcase for this? gem_exec_parse/allocations was written to show a performance cliff wrt to an older implementation of the batch_pool cache. gem_exec_parallel + async patching puts this nicely to use. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
