From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: Zoltan Menyhart <Zoltan.Menyhart@bull.net>,
"Boehm, Hans" <hans.boehm@hp.com>,
"Grundler, Grant G" <grant.grundler@hp.com>,
"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: Synchronizing Bit operations V2
Date: Fri, 31 Mar 2006 17:48:37 +0000 [thread overview]
Message-ID: <200603311948.38218.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0603310943480.6628@schroedinger.engr.sgi.com>
On Friday 31 March 2006 19:45, Christoph Lameter wrote:
> On Fri, 31 Mar 2006, Andi Kleen wrote:
>
> > Christoph Lameter <clameter@sgi.com> writes:
> > > MODE_BARRIER
> > > An atomic operation that is guaranteed to occur between
> > > previous and later memory operations.
> > I think it's a bad idea to create such an complicated interface.
> > The chances that an average kernel coder will get these right are
> > quite small. And it will be 100% untested outside IA64 I guess
> > and thus likely be always slightly buggy as kernel code continues
> > to change.
>
> Powerpc can do similar things AFAIK. Not sure what other arches have
> finer grained control over barriers but it could cover a lot of special
> cases for other processors as well.
Yes, but I don't think the goal of a portable atomic operations API
in Linux is it to cover everybody's special case in every possible
combination. The goal is to have an abstraction that will lead to
portable code. I don't think your proposal will do this.
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: Zoltan Menyhart <Zoltan.Menyhart@bull.net>,
"Boehm, Hans" <hans.boehm@hp.com>,
"Grundler, Grant G" <grant.grundler@hp.com>,
"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: Synchronizing Bit operations V2
Date: Fri, 31 Mar 2006 19:48:37 +0200 [thread overview]
Message-ID: <200603311948.38218.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0603310943480.6628@schroedinger.engr.sgi.com>
On Friday 31 March 2006 19:45, Christoph Lameter wrote:
> On Fri, 31 Mar 2006, Andi Kleen wrote:
>
> > Christoph Lameter <clameter@sgi.com> writes:
> > > MODE_BARRIER
> > > An atomic operation that is guaranteed to occur between
> > > previous and later memory operations.
> > I think it's a bad idea to create such an complicated interface.
> > The chances that an average kernel coder will get these right are
> > quite small. And it will be 100% untested outside IA64 I guess
> > and thus likely be always slightly buggy as kernel code continues
> > to change.
>
> Powerpc can do similar things AFAIK. Not sure what other arches have
> finer grained control over barriers but it could cover a lot of special
> cases for other processors as well.
Yes, but I don't think the goal of a portable atomic operations API
in Linux is it to cover everybody's special case in every possible
combination. The goal is to have an abstraction that will lead to
portable code. I don't think your proposal will do this.
-Andi
next prev parent reply other threads:[~2006-03-31 17:48 UTC|newest]
Thread overview: 124+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 21:02 Bit operations with the ability to specify a synchronization mode Christoph Lameter
2006-03-30 21:02 ` Christoph Lameter
2006-03-31 0:18 ` Synchronizing Bit operations V2 Christoph Lameter
2006-03-31 0:18 ` Christoph Lameter
2006-03-31 0:39 ` Chen, Kenneth W
2006-03-31 0:39 ` Chen, Kenneth W
2006-03-31 0:42 ` Christoph Lameter
2006-03-31 0:42 ` Christoph Lameter
2006-03-31 0:45 ` Christoph Lameter
2006-03-31 0:45 ` Christoph Lameter
2006-03-31 0:42 ` David Mosberger-Tang
2006-03-31 0:42 ` David Mosberger-Tang
2006-03-31 0:49 ` Christoph Lameter
2006-03-31 0:49 ` Christoph Lameter
2006-03-31 6:10 ` Chris Wright
2006-03-31 6:10 ` Chris Wright
2006-03-31 0:44 ` Nick Piggin
2006-03-31 0:44 ` Nick Piggin
2006-03-31 3:28 ` Christoph Lameter
2006-03-31 3:28 ` Christoph Lameter
2006-03-31 4:12 ` Nick Piggin
2006-03-31 4:12 ` Nick Piggin
2006-03-31 17:43 ` Christoph Lameter
2006-03-31 17:43 ` Christoph Lameter
2006-04-01 2:56 ` Nick Piggin
2006-04-01 2:56 ` Nick Piggin
2006-03-31 0:50 ` Chen, Kenneth W
2006-03-31 0:50 ` Chen, Kenneth W
2006-03-31 0:51 ` Christoph Lameter
2006-03-31 0:51 ` Christoph Lameter
2006-03-31 0:53 ` Chen, Kenneth W
2006-03-31 0:53 ` Chen, Kenneth W
2006-03-31 0:55 ` Christoph Lameter
2006-03-31 0:55 ` Christoph Lameter
2006-03-31 0:56 ` Luck, Tony
2006-03-31 0:56 ` Luck, Tony
2006-03-31 0:58 ` Christoph Lameter
2006-03-31 0:58 ` Christoph Lameter
2006-04-02 7:59 ` Russell King
2006-04-02 7:59 ` Russell King
2006-03-31 0:59 ` Chen, Kenneth W
2006-03-31 0:59 ` Chen, Kenneth W
2006-03-31 1:09 ` Christoph Lameter
2006-03-31 1:09 ` Christoph Lameter
2006-03-31 1:04 ` Chen, Kenneth W
2006-03-31 1:04 ` Chen, Kenneth W
2006-03-31 1:13 ` Christoph Lameter
2006-03-31 1:13 ` Christoph Lameter
2006-03-31 1:13 ` Chen, Kenneth W
2006-03-31 1:13 ` Chen, Kenneth W
2006-03-31 1:29 ` Chen, Kenneth W
2006-03-31 1:29 ` Chen, Kenneth W
2006-03-31 1:37 ` Christoph Lameter
2006-03-31 1:37 ` Christoph Lameter
2006-03-31 1:33 ` linux
2006-03-31 1:33 ` linux
2006-03-31 1:40 ` Christoph Lameter
2006-03-31 1:40 ` Christoph Lameter
2006-03-31 2:35 ` Chen, Kenneth W
2006-03-31 2:35 ` Chen, Kenneth W
2006-03-31 2:37 ` Christoph Lameter
2006-03-31 2:37 ` Christoph Lameter
2006-03-31 2:45 ` Chen, Kenneth W
2006-03-31 2:45 ` Chen, Kenneth W
2006-03-31 2:53 ` Nick Piggin
2006-03-31 2:53 ` Nick Piggin
2006-03-31 3:01 ` Christoph Lameter
2006-03-31 3:01 ` Christoph Lameter
2006-03-31 2:51 ` Chen, Kenneth W
2006-03-31 2:51 ` Chen, Kenneth W
2006-03-31 2:55 ` Christoph Lameter
2006-03-31 2:55 ` Christoph Lameter
2006-03-31 3:02 ` Chen, Kenneth W
2006-03-31 3:02 ` Chen, Kenneth W
2006-03-31 3:08 ` Christoph Lameter
2006-03-31 3:08 ` Christoph Lameter
2006-03-31 3:10 ` Chen, Kenneth W
2006-03-31 3:10 ` Chen, Kenneth W
2006-03-31 3:12 ` Christoph Lameter
2006-03-31 3:12 ` Christoph Lameter
2006-03-31 3:11 ` Chen, Kenneth W
2006-03-31 3:11 ` Chen, Kenneth W
2006-03-31 3:14 ` Chen, Kenneth W
2006-03-31 3:14 ` Chen, Kenneth W
2006-03-31 3:20 ` Christoph Lameter
2006-03-31 3:20 ` Christoph Lameter
2006-03-31 3:17 ` Chen, Kenneth W
2006-03-31 3:17 ` Chen, Kenneth W
2006-03-31 3:23 ` Chen, Kenneth W
2006-03-31 3:23 ` Chen, Kenneth W
2006-03-31 3:37 ` Chen, Kenneth W
2006-03-31 3:37 ` Chen, Kenneth W
2006-03-31 6:15 ` Chen, Kenneth W
2006-03-31 6:15 ` Chen, Kenneth W
2006-03-31 7:34 ` Nick Piggin
2006-03-31 7:34 ` Nick Piggin
2006-03-31 13:28 ` Andi Kleen
2006-03-31 13:28 ` Andi Kleen
2006-03-31 16:22 ` Hans Boehm
2006-03-31 16:22 ` Hans Boehm
2006-03-31 16:37 ` Andi Kleen
2006-03-31 16:37 ` Andi Kleen
2006-03-31 17:46 ` Christoph Lameter
2006-03-31 17:46 ` Christoph Lameter
2006-03-31 17:45 ` Christoph Lameter
2006-03-31 17:45 ` Christoph Lameter
2006-03-31 17:48 ` Andi Kleen [this message]
2006-03-31 17:48 ` Andi Kleen
2006-03-31 17:56 ` Christoph Lameter
2006-03-31 17:56 ` Christoph Lameter
2006-04-02 7:54 ` Russell King
2006-04-02 7:54 ` Russell King
2006-03-31 18:57 ` Chen, Kenneth W
2006-03-31 18:57 ` Chen, Kenneth W
2006-03-31 19:41 ` Chen, Kenneth W
2006-03-31 19:41 ` Chen, Kenneth W
2006-03-31 21:15 ` Christoph Lameter
2006-03-31 21:15 ` Christoph Lameter
2006-03-31 21:24 ` Chen, Kenneth W
2006-03-31 21:24 ` Chen, Kenneth W
2006-03-31 21:28 ` Christoph Lameter
2006-03-31 21:28 ` Christoph Lameter
2006-04-01 2:16 ` Nick Piggin
2006-04-01 2:16 ` Nick Piggin
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=200603311948.38218.ak@suse.de \
--to=ak@suse.de \
--cc=Zoltan.Menyhart@bull.net \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=grant.grundler@hp.com \
--cc=hans.boehm@hp.com \
--cc=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.