lkml.org 
[lkml]   [2020]   [Nov]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH tip/core/rcu 1/4] doc: Present the role of READ_ONCE()
On Mon, Nov 09, 2020 at 01:21:33PM +0100, Peter Zijlstra wrote:
> On Thu, Nov 05, 2020 at 03:05:07PM -0800, paulmck@kernel.org wrote:
> > From: "Paul E. McKenney" <paulmck@kernel.org>
> >
> > This commit adds an explanation of the special cases where READ_ONCE()
> > may be used in place of a member of the rcu_dereference() family.
>
> I am confused, there is no actual difference between rcu_dereference()
> and READ_ONCE() today. So we _may_ use READ_ONCE() at all times.
>
> Now granted, we probably don't want that, but that does leave me
> somewhat confused vs the wording here.

There is a difference from the viewpoint of both lockdep and sparse.

Or am I missing your point?

Thanx, Paul

\
 
 \ /
  Last update: 2020-11-09 17:21    [W:0.037 / U:0.944 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site