All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: tglx@linutronix.de, linux-rt-users@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: rcu: Merge RCU-bh into RCU-preempt
Date: Thu, 8 Nov 2018 08:42:47 -0800	[thread overview]
Message-ID: <20181108164247.GL4170@linux.ibm.com> (raw)
In-Reply-To: <20181108160256.xpawe65h5lm65soi@linutronix.de>

On Thu, Nov 08, 2018 at 05:02:57PM +0100, Sebastian Andrzej Siewior wrote:
> On 2018-11-01 16:18:04 [-0700], Paul E. McKenney wrote:
> > The need for this goes away as of the current merge window because
> > RCU-bh has gone away.  (Aside from still being able to do things
> > like rcu_read_lock_bh() as a documentation device.)
> 
> So in -RT rcu_read_lock_bh() does
>  { local_bh_disable() ;  rcu_read_lock() }
> 
> So you are saying that this is also the case in v4.20?

No, rcu_read_lock_bh() and rcu_read_unlock_bh() are unchanged in v4.20.
With the new RCU grace-period mechanism, local_bh_disable() blocks future
grace periods on its own.

Unless I am missing something (quite probable, actually), the v4.20
definitions of rcu_read_lock_bh() and rcu_read_unlock_bh() should work
as-is for -rt.

							Thanx, Paul

  reply	other threads:[~2018-11-08 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01 23:18 rcu: Merge RCU-bh into RCU-preempt Paul E. McKenney
2018-11-08 16:02 ` Sebastian Andrzej Siewior
2018-11-08 16:42   ` Paul E. McKenney [this message]
2018-11-08 17:15     ` Sebastian Andrzej Siewior
2018-11-08 17:35       ` Paul E. McKenney
2018-11-08 17:48         ` Sebastian Andrzej Siewior

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=20181108164247.GL4170@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.