All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Frederic Weisbecker <fweisbec@gmail.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, josh@joshtriplett.org,
	rostedt <rostedt@goodmis.org>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	mingo@redhat.com
Subject: Re: Isolated expedited RCU code to a new tree_exp.h
Date: Sat, 16 Apr 2016 15:29:09 +0000 (UTC)	[thread overview]
Message-ID: <1388559142.60584.1460820549723.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20160416130831.GA29917@lerouge>

----- On Apr 16, 2016, at 9:08 AM, Frederic Weisbecker fweisbec@gmail.com wrote:

> On Fri, Apr 15, 2016 at 04:52:02PM -0700, Paul E. McKenney wrote:
>> 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?
> 
> It's definetly worth having a look! And it might help me eventually understand
> that expedited grace period thing :-)

Moving the expedited handling into its own files indeed
seems to better organize the sub-parts of RCU. That seems
like a good idea.

Thanks,

Mathieu


-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

  reply	other threads:[~2016-04-16 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 23:52 Isolated expedited RCU code to a new tree_exp.h Paul E. McKenney
2016-04-16 13:08 ` Frederic Weisbecker
2016-04-16 15:29   ` Mathieu Desnoyers [this message]
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=1388559142.60584.1460820549723.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=fweisbec@gmail.com \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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 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.