lkml.org 
[lkml]   [2014]   [Jun]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH RFC] percpu: add data dependency barrier in percpu accessors and operations
On Thu, Jun 19, 2014 at 03:42:07PM -0500, Christoph Lameter wrote:
> In that case special care needs to be taken to get this right. True.
>
> I typically avoid these scenarios by sending an IPI with a pointer to the
> data structure. The modification is done by the cpu for which the per cpu
> data is local.
>
> Maybe rewrite the code to avoid writing to other processors percpu data
> would be the right approach?

It depends on the specific use case but in general no. IPIs would be
far more expensive than making use of proper barriers in vast majority
of cases especially when the "hot" side is data dependency barrier,
IOW, nothing. Also, we are talking about extremely low frequency
events like init and recycling after reinit. Regular per-cpu
operation isn't really the subject here.

Thanks.

--
tejun


\
 
 \ /
  Last update: 2014-06-20 04:21    [W:0.066 / U:33.620 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site