[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1012251753530.8506@router.home>
Date: Sat, 25 Dec 2010 17:55:22 -0600 (CST)
From: Christoph Lameter <cl@...ux.com>
To: Tejun Heo <tj@...nel.org>
cc: "H. Peter Anvin" <hpa@...or.com>, akpm@...ux-foundation.org,
Pekka Enberg <penberg@...helsinki.fi>,
linux-kernel@...r.kernel.org,
Eric Dumazet <eric.dumazet@...il.com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: Re: [cpuops cmpxchg double V1 1/4] Generic support for
this_cpu_cmpxchg_double
On Sat, 25 Dec 2010, Tejun Heo wrote:
> ABI. But that said, it might still be problematic on other
> architectures when we try to apply it to different architectures. Is
> everyone against just taking a scalar for the first variable instead
> of taking a pointer? I'd be happier with that than the current one.
How about replacing that with two scalars? Macro will check that the
scalaers are properly aligned and that the second follows the first. Then
there is also better symmetry in the parameters.
bool this_cpu_cmpxchg_double(
percpu_1, percpu_2
old_1, old_2
new_1, new_2
)
--
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