Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1343209

Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical sections

From Peter Zijlstra <peterz@infradead.org>
Newsgroups linux.kernel
Subject Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical sections
Date 2016-02-25 15:40 +0100
Message-ID <r65fc-59a-21@gated-at.bofh.it> (permalink)
References <r2GQ3-3tt-15@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Tue, Feb 16, 2016 at 01:57:39PM +0800, Boqun Feng wrote:
> As a characteristic of RCU, read-side critical sections have a very
> loose connection with rcu_dereference()s, which is you can only be sure
> about an rcu_dereference() might be called in some read-side critical
> section, but if code gets complex, you may not be sure which read-side
> critical section exactly, this might be also an problem for some other
> locking mechanisms, that is the critical sections protecting data and
> the data accesses protected are not clearly correlated.
> 
> In this series, we are introducing LOCKED_ACCESS framework and based on
> which, we implement the RCU_LOCKED_ACCESS functionality to give us a
> clear hint: which rcu_dereference() happens in which RCU read-side
> critical section. 
> 
> After this series applied, and if CONFIG_RCU_LOCKED_ACCESS=y, the proc
> file /proc/locked_access/rcu will show all relationships collected so
> far for rcu_read_lock() and their friends and rcu_dereference*().
> 

But why !? What does this bring us, why do I want to even look at these
patches?

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical  sections Peter Zijlstra <peterz@infradead.org> - 2016-02-25 15:40 +0100
  Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical  sections "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-02-25 16:40 +0100
    Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical  sections Boqun Feng <boqun.feng@gmail.com> - 2016-02-26 04:10 +0100
      Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical  sections Peter Zijlstra <peterz@infradead.org> - 2016-02-26 12:30 +0100
        Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical  sections Boqun Feng <boqun.feng@gmail.com> - 2016-02-29 02:20 +0100
          Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical  sections Peter Zijlstra <peterz@infradead.org> - 2016-02-29 13:50 +0100
            Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical  sections Boqun Feng <boqun.feng@gmail.com> - 2016-03-01 10:40 +0100
              Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical  sections Peter Zijlstra <peterz@infradead.org> - 2016-03-01 11:00 +0100
                Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical  sections Peter Zijlstra <peterz@infradead.org> - 2016-03-01 11:10 +0100
                Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical  sections Boqun Feng <boqun.feng@gmail.com> - 2016-03-02 07:40 +0100
                Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical  sections Peter Zijlstra <peterz@infradead.org> - 2016-03-02 11:20 +0100
                Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical  sections "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-03-02 15:10 +0100

csiph-web