From: Oleg Nesterov <oleg@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Josh Triplett <josh@joshtriplett.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] rcu: uninline rcu_lock_acquire() and rcu_lock_release()
Date: Thu, 26 Jun 2014 19:01:16 +0200 [thread overview]
Message-ID: <20140626170116.GA28558@redhat.com> (raw)
Hello,
sorry for delay with resend...
The patch is simple and the numbers look good (and probably we can do more).
But when I re-diffed this change I noticed that rcu_lockdep_assert() has the
warn-once semantics, and this patch obviously changes the behaviour. So please
ack/nack this part too.
Oleg.
next reply other threads:[~2014-06-26 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 17:01 Oleg Nesterov [this message]
2014-06-26 17:01 ` [PATCH 1/1] rcu: uninline rcu_lock_acquire() and rcu_lock_release() Oleg Nesterov
2014-06-26 17:33 ` [PATCH v2 " Oleg Nesterov
2014-06-26 18:36 ` [PATCH v3 " Oleg Nesterov
2014-06-26 19:21 ` Paul E. McKenney
2014-06-26 19:43 ` Oleg Nesterov
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=20140626170116.GA28558@redhat.com \
--to=oleg@redhat.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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