From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: [SOLVED + PATCH]: documented Oops running big-endian reiserfs on parisc architecture
Date: Sat, 8 Sep 2001 01:41:44 +0000 (UTC) [thread overview]
Message-ID: <9nbt0o$o5s$1@penguin.transmeta.com> (raw)
In-Reply-To: <OF9A995335.07A81CF5-ONC1256ABC.00422A7B@de.ibm.com> <20010903.152443.59467554.davem@redhat.com>
In article <20010903.152443.59467554.davem@redhat.com>,
David S. Miller <davem@redhat.com> wrote:
>
>Oh thats different! That won't even work %100 correctly on x86. On
>x86 it will "execute", but it won't be atomic.
Actually, it will. Intel definitely discourages it, but they'll lock
both cache-lines if the access is unaligned and crosses. So while they
encourage natural alignment for atomic accesses, I think they also
guarantee that they always work - it ends up being only a performance
issue.
I agree that it is bad practice, though, and I bet that the x86 is one
of the very few architectures that _will_ do this naturally.
Linus
next prev parent reply other threads:[~2001-09-08 1:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 12:08 [SOLVED + PATCH]: documented Oops running big-endian reiserfs on parisc architecture Ulrich Weigand
2001-09-03 13:14 ` Ralf Baechle
2001-09-03 22:24 ` David S. Miller
2001-09-08 1:41 ` Linus Torvalds [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-04 22:55 Ulrich Weigand
2001-09-04 17:04 Ulrich Weigand
2001-09-04 14:34 Ulrich Weigand
2001-09-04 15:02 ` Richard B. Johnson
2001-09-04 16:09 ` John Alvord
[not found] <20010902105538.A15344@middle.of.nowhere.suse.lists.linux.kernel>
[not found] ` <20010902150023.U5126@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel>
[not found] ` <20010902195717.A21209@middle.of.nowhere.suse.lists.linux.kernel>
[not found] ` <20010903003437.A385@linux-m68k.org.suse.lists.linux.kernel>
[not found] ` <20010903213835.A13887@fury.csh.rit.edu.suse.lists.linux.kernel>
2001-09-04 9:44 ` Andi Kleen
2001-09-04 10:04 ` David S. Miller
2001-09-04 10:25 ` Andi Kleen
2001-09-04 10:29 ` David S. Miller
2001-09-04 12:50 ` Jeff Mahoney
2001-09-02 8:55 thunder7
2001-09-02 14:00 ` [parisc-linux] " Matthew Wilcox
2001-09-02 17:57 ` [SOLVED + PATCH]: " thunder7
2001-09-02 22:34 ` Richard Zidlicky
2001-09-02 23:08 ` David S. Miller
2001-09-04 1:38 ` Jeff Mahoney
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='9nbt0o$o5s$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox