From: Andrea Arcangeli <andrea@suse.de>
To: Stephen Hemminger <shemminger@osdl.org>,
Andrew Morton <akpm@digeo.com>, Andi Kleen <ak@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: frlock and barrier discussion
Date: Fri, 31 Jan 2003 01:57:47 +0100 [thread overview]
Message-ID: <20030131005746.GA18538@dualathlon.random> (raw)
In-Reply-To: <20030130164120.A22148@twiddle.net>
On Thu, Jan 30, 2003 at 04:41:20PM -0800, Richard Henderson wrote:
> On Thu, Jan 30, 2003 at 02:52:19AM +0100, Andrea Arcangeli wrote:
> > you're missing xtimensec is a write.
>
> Eh? xtimensec is a register.
then it's fine, the register will be flushed to ram eventually and it
will be within the two wmb(), just write in the example also the line
where the xtimensec ""register"" is flushed to ram and it will be in the
right place
if the register isn't flushed to ram eventually, it will be discared and
the whole critical section is a noop from the point of view of the other
cpus and no wmb() or rmb() or mb() would be needed in the first place
Andrea
next prev parent reply other threads:[~2003-01-31 0:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 23:42 [PATCH] (1/4) 2.5.59 fast reader/writer lock for gettimeofday Stephen Hemminger
2003-01-29 7:06 ` Richard Henderson
2003-01-29 7:26 ` Anton Blanchard
2003-01-29 8:41 ` Andrew Morton
2003-01-30 1:15 ` frlock and barrier discussion Stephen Hemminger
2003-01-30 1:29 ` Andrea Arcangeli
2003-01-30 1:41 ` Richard Henderson
2003-01-30 1:52 ` Andrea Arcangeli
2003-01-31 0:41 ` Richard Henderson
2003-01-31 0:57 ` Andrea Arcangeli [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-30 18:20 Manfred Spraul
2003-01-30 18:26 ` Andrea Arcangeli
2003-01-30 19:05 ` Manfred Spraul
2003-01-30 19:54 ` Davide Libenzi
2003-01-30 22:32 ` Alan Cox
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=20030131005746.GA18538@dualathlon.random \
--to=andrea@suse.de \
--cc=ak@suse.de \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox