From: Johannes Weiner <hannes@saeurebad.de>
To: "Peter Teoh" <htmldeveloper@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: spin_lock after get_cpu_var()
Date: Sun, 16 Mar 2008 11:12:45 +0100 [thread overview]
Message-ID: <87ve3n0yg2.fsf@saeurebad.de> (raw)
In-Reply-To: <804dabb00803160124p1240abe1v842821e988fdeca7@mail.gmail.com> (Peter Teoh's message of "Sun, 16 Mar 2008 16:24:02 +0800")
Hi Peter,
"Peter Teoh" <htmldeveloper@gmail.com> writes:
> I find it quite puzzling (no where else in kernel source is this
> found) that you would want to apply spin_lock() after get_cpu_var().
> The fddef is already percpu, so there is no need to lock it, right?
>
> I submitted this patch before, but got no response, just trying my
> luck this time :-).
http://lkml.org/lkml/2008/3/14/208
Hannes
prev parent reply other threads:[~2008-03-16 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 8:24 spin_lock after get_cpu_var() Peter Teoh
2008-03-16 10:12 ` Johannes Weiner [this message]
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=87ve3n0yg2.fsf@saeurebad.de \
--to=hannes@saeurebad.de \
--cc=htmldeveloper@gmail.com \
--cc=linux-kernel@vger.kernel.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