All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junchang Wang <junchangwang@gmail.com>
To: perfbook@vger.kernel.org
Cc: paulmck@linux.ibm.com, akiyks@gmail.com
Subject: Question about the detection of overflow in rcu_nest:rcu_read_lock()
Date: Thu, 25 Apr 2019 17:25:28 +0800	[thread overview]
Message-ID: <20190425092526.GA17338@PhD> (raw)

Hi list,

I was reading rcu_nest.h and the code snippet (lines 59 - 63), which I believe
is to detect the overflow of variable rcu_gp_ctr, confused me a lot. Can some
of you shed light on that?

Specifically, what's the goal of line 60? Why should we compare the value of
(rcu_gp_ctr - tmp) against "111 1111 0000 0000"? If I understand correctly,
line 60 is to detect the scenario where rcu_gp_ctr has wrapped around and is
currently smaller than variable tmp. If that is correct, should line 60 be the
following?

60             ((tmp - READ_ONCE(rcu_gp_ctr)) > RCU_GP_CTR_BOTTOM_BIT) {

Or did I misunderstand anything here? 

 40 static void rcu_read_lock(void)
 41 {
 42         long tmp;
 43         long *rrgp;
 44 
 45         /*
 46          * If this is the outermost RCU read-side critical section,
 47          * copy the global grace-period counter.  In either case,
 48          * increment the nesting count held in the low-order bits.
 49          */
 50 
 51         rrgp = &__get_thread_var(rcu_reader_gp);
 52 retry:
 53         tmp = *rrgp;
 54         if ((tmp & RCU_GP_CTR_NEST_MASK) == 0)
 55                 tmp = READ_ONCE(rcu_gp_ctr);
 56         tmp++;
 57         *rrgp = tmp;
 58         smp_mb();
 59         if (((tmp & RCU_GP_CTR_NEST_MASK) == 1) &&
 60             ((rcu_gp_ctr - tmp) > (RCU_GP_CTR_NEST_MASK << 8)) != 0) {
 61                 (*rrgp)--;
 62                 goto retry;
 63         }
 64 }

Thanks,
--Junchang


             reply	other threads:[~2019-04-25  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25  9:25 Junchang Wang [this message]
2019-04-28 11:30 ` Question about the detection of overflow in rcu_nest:rcu_read_lock() Paul E. McKenney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190425092526.GA17338@PhD \
    --to=junchangwang@gmail.com \
    --cc=akiyks@gmail.com \
    --cc=paulmck@linux.ibm.com \
    --cc=perfbook@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.