From: "Christopher Friesen" <cfriesen@nortel.com>
To: linux@horizon.com
Cc: dev@sw.ru, linux-kernel@vger.kernel.org
Subject: Re: SMP syncronization on AMD processors (broken?)
Date: Tue, 11 Oct 2005 20:12:28 -0600 [thread overview]
Message-ID: <434C710C.2040305@nortel.com> (raw)
In-Reply-To: <20051011235017.21719.qmail@science.horizon.com>
linux@horizon.com wrote:
> The right thing to do here is to wait for the flag to be set *outside*
> the lock, and then re-validate inside the lock:
This may work on some processors, but on others the read of "progress"
in XXX, or the write in YYY may require arch-specific code to force the
update out to other cpus.
Alternately, explicitly atomic operations should suffice, but a simple
increment is probably not enough for portable code.
Chris
next prev parent reply other threads:[~2005-10-12 2:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 23:50 SMP syncronization on AMD processors (broken?) linux
2005-10-12 2:12 ` Christopher Friesen [this message]
2005-10-12 2:39 ` linux
2005-10-12 3:27 ` Kyle Moffett
2005-10-13 12:25 ` Kirill Korotaev
-- strict thread matches above, loose matches on Subject: below --
2005-10-08 9:31 Chuck Ebbert
2005-10-06 13:05 Kirill Korotaev
2005-10-06 13:14 ` linux-os (Dick Johnson)
2005-10-06 13:19 ` Arjan van de Ven
2005-10-06 13:32 ` Andrey Savochkin
2005-10-06 14:22 ` Arjan van de Ven
2005-10-06 13:32 ` Andi Kleen
2005-10-06 13:46 ` Andrey Savochkin
2005-10-06 14:52 ` Linus Torvalds
2005-10-06 15:21 ` Andrey Savochkin
2005-10-06 15:46 ` Linus Torvalds
2005-10-11 0:59 ` Andrew Morton
2005-10-11 1:20 ` Andi Kleen
2005-10-11 3:20 ` Joe Seigh
2005-10-06 13:50 ` Eric Dumazet
2005-10-06 14:45 ` Linus Torvalds
2005-10-06 15:34 ` Hugh Dickins
2005-10-06 15:53 ` Eric Dumazet
2005-10-06 16:01 ` Linus Torvalds
2005-10-07 20:38 ` Joe Seigh
2005-10-07 20:57 ` Stephen Hemminger
2005-10-13 18:24 ` Joe Seigh
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=434C710C.2040305@nortel.com \
--to=cfriesen@nortel.com \
--cc=dev@sw.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
/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.