mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: josh@joshtriplett.org, rostedt@goodmis.org,
	mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
	joel@joelfernandes.org, bigeasy@linutronix.de,
	tglx@linutronix.de, swood@redhat.com, williams@redhat.com,
	juri.lelli@redhat.com, linux-rt-users@vger.kernel.org
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org, mingo@kernel.org
Subject: RCU use of swait
Date: Wed, 4 Mar 2020 16:35:26 -0800	[thread overview]
Message-ID: <20200305003526.GA20601@paulmck-ThinkPad-P72> (raw)

Hello!

RCU makes considerable use of swait and friends.  The motivation I recall
was around offloaded callbacks, where in the old days the grace-period
kthread might do a wakeup for up to N tasks, where N is the number of
CPUs, all with interrupts disabled.  This has since been reduced to
roughly sqrt(N) tasks, which might well still be too many wakeups to do
with interrupts disabled throughout.

However, the other use cases have at most one waiter to be awakened.

So I am guessing that I could usefully convert all but the rcu_node
structure's ->nocb_gp_wq field from swait to wait.  Particularly the
use cases in SRCU and Tiny RCU.

Or is there some other reason why {S,}RCU needs to use swait that I
am forgetting?

							Thanx, Paul

             reply	other threads:[~2020-03-05  0:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05  0:35 Paul E. McKenney [this message]
2020-03-05  8:11 ` Sebastian Andrzej Siewior
2020-03-19  0:47   ` Joel Fernandes
2020-03-19  9:25     ` 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=20200305003526.GA20601@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=swood@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®