From: Joel Fernandes <joelaf@google.com>
To: linux-kernel@vger.kernel.org
Cc: Joel Fernandes <joel@joelfernandes.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
byungchul.park@lge.com, kernel-team@android.com
Subject: [PATCH v2 0/4] fixes, cleanups for rcu/dev
Date: Sun, 20 May 2018 21:32:47 -0700 [thread overview]
Message-ID: <20180521043251.120953-1-joel@joelfernandes.org> (raw)
Hi Paul,
Here are some patches reworked with a few comments on few of the patches
from previous series: https://lkml.org/lkml/2018/5/13/296
4/4 is a new addition which fixes a potential issue.
Let me know what you think, thanks!
Joel Fernandes (4):
rcu: Add comment documenting how rcu_seq_snap works
rcu: Cleanup the variables used to request a new grace period
rcu: Use better variable names in funnel locking loop
rcu: Unlock non-start node only after accessing its gp_seq_needed
include/trace/events/rcu.h | 15 +++----
kernel/rcu/rcu.h | 33 +++++++++++++++-
kernel/rcu/tree.c | 80 +++++++++++++++++++++-----------------
3 files changed, 85 insertions(+), 43 deletions(-)
--
2.17.0.441.gb46fe60e1d-goog
next reply other threads:[~2018-05-21 4:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 4:32 Joel Fernandes [this message]
2018-05-21 4:32 ` [PATCH v2 1/4] rcu: Speed up calling of RCU tasks callbacks Joel Fernandes
2018-05-21 4:32 ` [PATCH v2 2/4] rcu: Add comment documenting how rcu_seq_snap works Joel Fernandes
2018-05-21 4:32 ` [PATCH v2 3/4] rcu: Cleanup the variables used to request a new grace period Joel Fernandes
2018-05-21 4:32 ` [PATCH v2 4/4] rcu: Use better variable names in funnel locking loop Joel Fernandes
2018-05-21 4:38 ` [PATCH v2 0/4] fixes, cleanups for rcu/dev Joel Fernandes
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=20180521043251.120953-1-joel@joelfernandes.org \
--to=joelaf@google.com \
--cc=byungchul.park@lge.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.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 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®