From: Ralf Baechle <ralf@linux-mips.org>
To: Mathieu Desnoyers <compudj@krystal.dyndns.org>
Cc: linux-kernel@vger.kernel.org, ltt-dev@shafik.org
Subject: Re: MIPS atomic operations, "sync"
Date: Fri, 10 Nov 2006 22:33:04 +0000 [thread overview]
Message-ID: <20061110223303.GA17712@linux-mips.org> (raw)
In-Reply-To: <20061110184049.GA24977@Krystal>
On Fri, Nov 10, 2006 at 01:40:49PM -0500, Mathieu Desnoyers wrote:
> I am currently creating a "LOCK" prefix free and memory barrier free version
> of atomic.h to fulfill my tracer (LTTng) needs, which is to atomically update
> per-cpu data and have a minimal performance loss.
>
> I just came across the MIPS atomic.h and system.h implementations in 2.6.18
> which brings a question :
>
> Why are the primitives in include/asm-mips/atomic.h using the "sync"
> instruction even in the UP case ? system.h cmpxchg only uses the sync in the
> SMP case.
Why are the standard atomic operations insufficient for your needs?
There is an enormous amout of subtilities in those atomic ops for some
architectures you probably do yourself a big favor by avoiding new
variants.
Ralf
next prev parent reply other threads:[~2006-11-10 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 18:40 MIPS atomic operations, "sync" Mathieu Desnoyers
2006-11-10 22:33 ` Ralf Baechle [this message]
2006-11-11 5:13 ` Mathieu Desnoyers
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=20061110223303.GA17712@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=compudj@krystal.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.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.