[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9c3a7c20906051234m499aefbrd1828a6bbee3caf9@mail.gmail.com>
Date: Fri, 5 Jun 2009 12:34:37 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: cl@...ux-foundation.org
Cc: linux-kernel@...r.kernel.org, Tejun Heo <tj@...nel.org>,
Eric Biederman <ebiederm@...stanetworks.com>,
Stephen Hemminger <shemminger@...tta.com>,
Trond Myklebust <Trond.Myklebust@...app.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
David L Stevens <dlstevens@...ibm.com>, mingo@...e.hu,
rusty@...tcorp.com.au, davem@...emloft.net,
"Sosnowski, Maciej" <maciej.sosnowski@...el.com>
Subject: Re: [this_cpu_xx 06/11] Eliminate get/put_cpu
[ added Maciej to the cc ]
On Fri, Jun 5, 2009 at 12:18 PM, <cl@...ux-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@...el.com>
Acked-by: Dan Williams <dan.j.williams@...el.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists