Re: [PATCH v3 1/4] lib/dlock-list: Distributed and lock-protected lists
From: Christoph Lameter
Date: Wed Jul 20 2016 - 20:48:34 EST
On Wed, 20 Jul 2016, Waiman Long wrote:
> Christoph, are you OK with Tejun's request to revert the name back to
> percpu_list? Or do you still think the current name is better?
The percpu structure contains a spinlock and may be remotely accessed? You
are aware that other percpu variables that share the same cacheline will
be negatively impacted by accesses from other processors?
The role of percpu areas are to have memory areas where the code can
expect that cachelines are exclusively there for that processor.
How frequent are the remote accesses? If this is rare then ok.