From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, jiangshanlai@gmail.com,
dipankar@in.ibm.com, akpm@linux-foundation.org,
mathieu.desnoyers@efficios.com, josh@joshtriplett.org,
tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org,
dhowells@redhat.com, edumazet@google.com, fweisbec@gmail.com,
oleg@redhat.com, bobby.prani@gmail.com
Subject: Re: [PATCH tip/core/rcu 0/3] Open-code trivial rcu_cblist accessors
Date: Tue, 2 May 2017 18:47:10 +0200 [thread overview]
Message-ID: <20170502164710.ayw3rx7vkuoxfwf6@gmail.com> (raw)
In-Reply-To: <20170502162114.GA12193@linux.vnet.ibm.com>
* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> Hello!
>
> And this series open-codes trivial rcu_cblist structure accessors:
>
> 1. Open-code rcu_cblist_empty(p) as !p->head.
>
> 2. Open-code rcu_cblist_n_cbs(p) as p->len.
>
> 3. Open-code rcu_cblist_n_lazy_cbs(p) as p->len_lazy.
>
>
> Thanx, Paul
>
> ------------------------------------------------------------------------
>
> rcu_segcblist.h | 20 +-------------------
> tree.c | 20 +++++++++-----------
> tree_plugin.h | 8 ++++----
> tree_trace.c | 4 ++--
> 4 files changed, 16 insertions(+), 36 deletions(-)
Ok, these all look good to me.
Thanks,
Ingo
next prev parent reply other threads:[~2017-05-02 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 16:21 Paul E. McKenney
2017-05-02 16:24 ` [PATCH tip/core/rcu 1/3] rcu: Open-code the rcu_cblist_empty() function Paul E. McKenney
2017-05-02 16:24 ` [PATCH tip/core/rcu 2/3] rcu: Open-code the rcu_cblist_n_cbs() function Paul E. McKenney
2017-05-02 16:24 ` [PATCH tip/core/rcu 3/3] rcu: Open-code the rcu_cblist_n_lazy_cbs() function Paul E. McKenney
2017-05-02 16:47 ` Ingo Molnar [this message]
2017-05-02 17:01 ` [PATCH tip/core/rcu 0/3] Open-code trivial rcu_cblist accessors 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=20170502164710.ayw3rx7vkuoxfwf6@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.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=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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 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®