From: Matthew Wilcox <matthew@wil.cx>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Pavel Machek <pavel@ucw.cz>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Andreas Dilger <adilger@clusterfs.com>,
"Theodore Ts'o" <tytso@mit.edu>,
"ext2-devel@lists.sourceforge.net"
<ext2-devel@lists.sourceforge.net>
Subject: Re: [Ext2-devel] Re: [Patch 7/10]: ext3 online resize: SMP locking for group metadata
Date: Fri, 1 Oct 2004 13:42:43 +0100 [thread overview]
Message-ID: <20041001124243.GA16153@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1096630838.2001.14.camel@sisko.scot.redhat.com>
On Fri, Oct 01, 2004 at 12:40:38PM +0100, Stephen C. Tweedie wrote:
> So I don't want to make it atomic if I can avoid it. It's just an
> unsigned long, and I don't know of any cases where a simple read
> colliding with a write is going to give the reader a corrupt value. As
> long as I get either the old or new value, everything should be fine
> with the read/write barriers as they are.
I think all Linux architectures guarantee atomic updates of a
register-sized naturally-aligned piece of memory.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
prev parent reply other threads:[~2004-10-01 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 13:23 Stephen Tweedie
2004-10-01 10:18 ` Pavel Machek
2004-10-01 11:40 ` Stephen C. Tweedie
2004-10-01 12:42 ` Matthew Wilcox [this message]
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=20041001124243.GA16153@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sct@redhat.com \
--cc=tytso@mit.edu \
/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
Powered by JetHome