From: Steffen Klassert <steffen.klassert@secunet.com>
To: Shan Wei <shanwei88@gmail.com>
Cc: Kernel-Maillist <linux-kernel@vger.kernel.org>,
linux-crypto@vger.kernel.org, cl@linux-foundation.org
Subject: Re: [PATCH v2 5/9] kernel: padata : use this_cpu_read per-cpu helper
Date: Sat, 3 Nov 2012 09:24:55 +0100 [thread overview]
Message-ID: <20121103082455.GB20868@secunet.com> (raw)
In-Reply-To: <5093EE63.5000005@gmail.com>
>
> @@ -204,8 +204,7 @@ static struct padata_priv *padata_get_next(struct parallel_data *pd)
> goto out;
> }
>
> - queue = per_cpu_ptr(pd->pqueue, smp_processor_id());
> - if (queue->cpu_index == next_queue->cpu_index) {
> + if (this_cpu_read(pd->pqueue->cpu_index) == next_queue->cpu_index) {
This runs with bottom halves off, so we can use __this_cpu_read here.
prev parent reply other threads:[~2012-11-03 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 16:01 [PATCH v2 5/9] kernel: padata : use this_cpu_read per-cpu helper Shan Wei
2012-11-02 17:46 ` Christoph Lameter
2012-11-03 8:24 ` Steffen Klassert [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=20121103082455.GB20868@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=cl@linux-foundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shanwei88@gmail.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