[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090115184625.GA9944@elte.hu>
Date: Thu, 15 Jan 2009 19:46:25 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Tejun Heo <tj@...nel.org>
Cc: "H. Peter Anvin" <hpa@...or.com>, Brian Gerst <brgerst@...il.com>,
ebiederm@...ssion.com, cl@...ux-foundation.org,
rusty@...tcorp.com.au, travis@....com,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
steiner@....com, hugh@...itas.com
Subject: Re: [PATCH] percpu: add optimized generic percpu accessors
* Tejun Heo <tj@...nel.org> wrote:
> From: Ingo Molnar <mingo@...e.hu>
>
> It is an optimization and a cleanup, and adds the following new
> generic percpu methods:
>
> percpu_read()
> percpu_write()
> percpu_add()
> percpu_sub()
> percpu_and()
> percpu_or()
> percpu_xor()
on a second thought ... i just started using this construct in code, and
promptly typoed it: i typed "per_cpu_read()".
Which is really the more logical name for this. Mind if i do a
s/percpu/per_cpu/ rename of all of these new APIs?
Ingo
--
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