From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: fweisbec@gmail.com
Cc: linux-kernel@vger.kernel.org, josh@joshtriplett.org,
rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
jiangshanlai@gmail.com, mingo@redhat.com
Subject: Isolated expedited RCU code to a new tree_exp.h
Date: Fri, 15 Apr 2016 16:52:02 -0700 [thread overview]
Message-ID: <20160415235202.GA26940@linux.vnet.ibm.com> (raw)
Hello, Frederic,
One thing that I have had on my list for some time is to rearrange the
RCU source code to make it easier to find things. Given our discussion
yesterday, this seemed like a good time to take that step with the
expedited grace-period code. I have a couple of commits doing this in
-rcu, and would like your opinion. Worthwhile, or should I revert those
two commits?
Thanx, Paul
next reply other threads:[~2016-04-15 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 23:52 Paul E. McKenney [this message]
2016-04-16 13:08 ` Isolated expedited RCU code to a new tree_exp.h Frederic Weisbecker
2016-04-16 15:29 ` Mathieu Desnoyers
2016-04-17 2:34 ` 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=20160415235202.GA26940@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.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 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.