From: William Lee Irwin III <wli@holomorphy.com>
To: Alex Zarochentsev <zam@namesys.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Roman Zippel <zippel@linux-m68k.org>, Paul Jackson <pj@sgi.com>,
Hans Reiser <reiser@namesys.com>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: 2.6.9-rc1-mm4 sparc reiser4 build broken - undefined atomic_sub_and_test
Date: Mon, 13 Sep 2004 19:06:14 -0700 [thread overview]
Message-ID: <20040914020614.GI9106@holomorphy.com> (raw)
In-Reply-To: <20040913171936.GC2252@backtop.namesys.com>
On Mon, Sep 13, 2004 at 03:58:37PM +0100, Hugh Dickins wrote:
>> sparc and s390 are not the only arches lacking atomic_sub_and_test.
>> Go ahead and send the patches changing all the arches that have it to
>> define __ARCH_HAS_ATOMIC_SUB_AND_TEST, and add asm-generic/atomic.h
>> for those that don't etc; but to me that seems like a waste of time -
>> unless Zam convinces us that Reiser4 will need every last ounce of
On Mon, Sep 13, 2004 at 09:19:36PM +0400, Alex Zarochentsev wrote:
> I do not, Hans will ;-)
> I just like to know what atomic.h common functions would be in 2.6.9+,
> because nowdays the API is not consisent accross the arches.
> atomic_sub_return() is OK.
sparc32 is very legacy; in a quick IRC poll of sparc32 users there was
approximately zero interest in new filesystems and most users used nfs
and/or ext[23]. One should note that as these cpus are very slow and
the systems have very little RAM compared to modern ones, kernel memory
footprint and the cpu complexity of fs operations for small fs's is of
high importance. I really don't expect reiser4 to ever be runtime
tested on sparc32. UltraSPARC is another matter entirely.
-- wli
next prev parent reply other threads:[~2004-09-14 2:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-12 10:12 2.6.9-rc1-mm4 sparc reiser4 build broken - undefined atomic_sub_and_test Paul Jackson
2004-09-12 10:54 ` William Lee Irwin III
2004-09-12 16:33 ` Alex Zarochentsev
2004-09-12 18:49 ` Paul Jackson
2004-09-12 19:48 ` Alex Zarochentsev
2004-09-13 12:42 ` Hugh Dickins
2004-09-13 13:25 ` Roman Zippel
2004-09-13 13:51 ` Hugh Dickins
2004-09-13 14:10 ` Roman Zippel
2004-09-13 14:58 ` Hugh Dickins
2004-09-13 16:03 ` Roman Zippel
2004-09-13 16:20 ` Hugh Dickins
2004-09-13 20:03 ` Tonnerre
2004-09-13 20:18 ` Roman Zippel
2004-09-13 20:18 ` 2.6.9-rc1-mm4 sparc reiser4 build broken - undefined atomic_s ub_and_test Hugh Dickins
2004-09-13 17:19 ` 2.6.9-rc1-mm4 sparc reiser4 build broken - undefined atomic_sub_and_test Alex Zarochentsev
2004-09-14 2:06 ` William Lee Irwin III [this message]
2004-09-14 9:00 ` Roman Zippel
2004-09-14 9:10 ` William Lee Irwin III
2004-09-14 9:15 ` [sparc32] add atomic_sub_and_test() to make reiser4 code microoptimized for x86 compile on sparc32 William Lee Irwin III
2004-09-14 15:38 ` William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2004-09-13 17:14 2.6.9-rc1-mm4 sparc reiser4 build broken - undefined atomic_sub_and_test Martin Schwidefsky
2004-09-13 17:26 ` Roman Zippel
[not found] <OF6D4E73AE.1DB1AD2F-ON42256F0F.003132FF-42256F0F.00321365@de.ibm.com>
2004-09-14 9:40 ` Roman Zippel
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=20040914020614.GI9106@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=reiser@namesys.com \
--cc=schwidefsky@de.ibm.com \
--cc=zam@namesys.com \
--cc=zippel@linux-m68k.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