From: Shan Wei <shanwei88@gmail.com>
To: Sven Eckelmann <sven@narfation.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org, lindner_marek@yahoo.de,
siwu@hrz.tu-chemnitz.de, ordex@autistici.org,
David Miller <davem@davemloft.net>,
NetDev <netdev@vger.kernel.org>,
Kernel-Maillist <linux-kernel@vger.kernel.org>,
Christoph Lameter <cl@linux.com>
Subject: Re: [B.A.T.M.A.N.] [PATCH v2 9/9] net: batman-adv: use per_cpu_add helper
Date: Sat, 03 Nov 2012 12:58:45 +0800 [thread overview]
Message-ID: <5094A485.4060409@gmail.com> (raw)
In-Reply-To: <5905519.yWN2Ke3YlE@bentobox>
Sven Eckelmann said, at 2012/11/3 1:55:
> On Saturday 03 November 2012 00:02:06 Shan Wei wrote:
>> From: Shan Wei <davidshan@tencent.com>
>>
>> As Christoph Lameter said:
>>> In addition, following usage of per_cpu_ptr can be replaced by
>>> this_cpu_read.
>>>
>>> cpu=get_cpu()
>>> ....
>>> *per_cpu_ptr(p,cpu)
>>> ....
>>> ....
>>> put_cpu()
>>
>> Right.
>>
>> Signed-off-by: Shan Wei <davidshan@tencent.com>
>> ---
>
> Is this really supposed to be the commit message?
Maybe it's ok when Linus said this. :-)
Christoph is the maintainer of per-cpu.
So........
PER-CPU MEMORY ALLOCATOR
M: Tejun Heo <tj@kernel.org>
M: Christoph Lameter <cl@linux-foundation.org>
T: git git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu.git
S: Maintained
F: include/linux/percpu*.h
F: mm/percpu*.c
F: arch/*/include/asm/percpu.h
>
> Kind regards,
> Sven
>
next prev parent reply other threads:[~2012-11-03 4:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 16:02 [PATCH v2 9/9] net: batman-adv: use per_cpu_add helper Shan Wei
2012-11-02 17:48 ` Christoph Lameter
2012-11-02 17:55 ` [B.A.T.M.A.N.] " Sven Eckelmann
2012-11-03 4:58 ` Shan Wei [this message]
2012-11-03 22:39 ` Sven Eckelmann
2012-11-05 15:19 ` 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=5094A485.4060409@gmail.com \
--to=shanwei88@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=cl@linux.com \
--cc=davem@davemloft.net \
--cc=lindner_marek@yahoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ordex@autistici.org \
--cc=siwu@hrz.tu-chemnitz.de \
--cc=sven@narfation.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