From: Dan Williams <dan.j.williams@intel.com>
To: cl@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
Eric Biederman <ebiederm@aristanetworks.com>,
Stephen Hemminger <shemminger@vyatta.com>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
David L Stevens <dlstevens@us.ibm.com>,
mingo@elte.hu, rusty@rustcorp.com.au, davem@davemloft.net,
"Sosnowski, Maciej" <maciej.sosnowski@intel.com>
Subject: Re: [this_cpu_xx 06/11] Eliminate get/put_cpu
Date: Fri, 5 Jun 2009 12:34:37 -0700 [thread overview]
Message-ID: <e9c3a7c20906051234m499aefbrd1828a6bbee3caf9@mail.gmail.com> (raw)
In-Reply-To: <20090605191851.393195588@gentwo.org>
[ added Maciej to the cc ]
On Fri, Jun 5, 2009 at 12:18 PM, <cl@linux-foundation.org> wrote:
> There are cases where we can use this_cpu_ptr and as the result
> of using this_cpu_ptr() we no longer need to determine the
> current executing cpu.
>
> In those places no get/put_cpu combination is needed anymore.
> The local cpu variable can be eliminated.
>
> Preemption still needs to be disabled and enabled since the
> modifications of the per cpu variables is not atomic. There may
> be multiple per cpu variables modified and those must all
> be from the same processor.
>
> cc: Dan Williams <dan.j.williams@intel.com>
Acked-by: Dan Williams <dan.j.williams@intel.com>
next prev parent reply other threads:[~2009-06-05 19:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 19:18 [this_cpu_xx 00/11] Introduce this_cpu_xx operations cl
2009-06-05 19:18 ` [this_cpu_xx 01/11] Introduce this_cpu_ptr() and generic this_cpu_* operations cl
2009-06-10 5:12 ` Tejun Heo
2009-06-11 15:10 ` Christoph Lameter
2009-06-12 2:09 ` Tejun Heo
2009-06-12 14:18 ` Christoph Lameter
2009-06-17 8:09 ` Tejun Heo
2009-06-17 8:19 ` Tejun Heo
2009-06-17 18:41 ` Christoph Lameter
2009-06-18 1:08 ` Tejun Heo
2009-06-18 3:01 ` Rusty Russell
2009-06-05 19:18 ` [this_cpu_xx 02/11] Use this_cpu operations for SNMP statistics cl
2009-06-05 19:18 ` [this_cpu_xx 03/11] Use this_cpu operations for NFS statistics cl
2009-06-05 19:18 ` [this_cpu_xx 04/11] Use this_cpu ops for network statistics cl
2009-06-08 11:27 ` Robin Holt
2009-06-08 20:49 ` Christoph Lameter
2009-06-08 20:54 ` Ingo Molnar
2009-06-05 19:18 ` [this_cpu_xx 05/11] this_cpu_ptr: Straight transformations cl
2009-06-05 19:18 ` [this_cpu_xx 06/11] Eliminate get/put_cpu cl
2009-06-05 19:34 ` Dan Williams [this message]
2009-06-09 14:02 ` Sosnowski, Maciej
2009-06-05 19:18 ` [this_cpu_xx 07/11] xfs_icsb_modify_counters does not need "cpu" variable cl
2009-06-05 19:22 ` Christoph Hellwig
2009-06-05 19:36 ` Christoph Lameter
2009-06-05 19:18 ` [this_cpu_xx 08/11] Use this_cpu_ptr in crypto subsystem cl
2009-06-05 19:18 ` [this_cpu_xx 09/11] X86 optimized this_cpu operations cl
2009-06-05 19:18 ` [this_cpu_xx 10/11] Use this_cpu ops for vm statistics cl
2009-06-05 19:18 ` [this_cpu_xx 11/11] RCU: Use this_cpu operations cl
2009-06-10 17:42 ` Paul E. McKenney
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=e9c3a7c20906051234m499aefbrd1828a6bbee3caf9@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=Trond.Myklebust@netapp.com \
--cc=cl@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=ebiederm@aristanetworks.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.sosnowski@intel.com \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@vyatta.com \
--cc=tj@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
all inboxes | Powered by JetHome®