On Tue, 28 Jul 2020 at 16:59, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote: > > Some very low hanging fruit, but contention on the pool->lock is > noticeable between intel_gt_get_buffer_pool() and pool_retire(), with > the majority of the hold time due to the locked list iteration. If we > make the node itself RCU protected, we can perform the search for an > suitable node just under RCU, reserving taking the lock itself for > claiming the node and manipulating the list. > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> Reviewed-by: Matthew Auld <matthew.auld@xxxxxxxxx> _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
