From: Tejun Heo <htejun@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: linux-kernel@vger.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Final per cpu consistency patch for -next or late in 3.19 merge period
Date: Tue, 2 Dec 2014 12:11:02 -0500 [thread overview]
Message-ID: <20141202171102.GC10918@htj.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1412021049580.13039@gentwo.org>
On Tue, Dec 02, 2014 at 10:57:50AM -0600, Christoph Lameter wrote:
> On Tue, 2 Dec 2014, Tejun Heo wrote:
>
> > Can you please update Documentation/local_ops.txt and comments which
> > contain __get_cpu_var() and send the updated patch to Andrew?
>
> Owww.... local_* ops are exotic operations that should no longer be
> regularly used. This_cpu ops create less overhead and
> are simpler to use. Lets merge the prior patch as is and then add this
> documentation patch which may cause some additional discussion.
Sure, I just wanna make sure we don't have dangling references to
__get_cpu_var() which no longer exists. There are also a couple
places where comment text refers to it. Let's please take care of
them too.
Thanks.
--
tejun
next prev parent reply other threads:[~2014-12-02 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 18:31 Final per cpu consistency patch for -next or late in 3.19 merge period Christoph Lameter
2014-12-02 16:40 ` Tejun Heo
2014-12-02 16:57 ` Christoph Lameter
2014-12-02 17:11 ` Tejun Heo [this message]
2014-12-02 17:32 ` Mathieu Desnoyers
2014-12-02 17:51 ` Christoph Lameter
2014-12-02 17:33 ` Christoph Lameter
2014-12-02 19:27 ` Luck, Tony
2014-12-02 17:34 ` Christoph Lameter
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=20141202171102.GC10918@htj.dyndns.org \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
/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