From: Roman Zippel <zippel@linux-m68k.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: hugh@veritas.com, zam@namesys.com, pj@sgi.com,
wli@holomorphy.com, reiser@namesys.com,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: 2.6.9-rc1-mm4 sparc reiser4 build broken - undefined atomic_sub_and_test
Date: Mon, 13 Sep 2004 19:26:57 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.61.0409131925100.877@scrub.home> (raw)
In-Reply-To: <20040913171435.GA3566@mschwid3.boeblingen.de.ibm.com>
Hi,
On Mon, 13 Sep 2004, Martin Schwidefsky wrote:
> Well, adding the missing s390 atomic operations is easy (see patch).
> But I really doubt that it will make a measurable difference in
> performance on ANY architecture.
On some archs atomic_sub_return is more complex than atomic_sub_and_test
and there it does make a difference.
bye, Roman
next prev parent reply other threads:[~2004-09-13 17:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 17:14 Martin Schwidefsky
2004-09-13 17:26 ` Roman Zippel [this message]
[not found] <OF6D4E73AE.1DB1AD2F-ON42256F0F.003132FF-42256F0F.00321365@de.ibm.com>
2004-09-14 9:40 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2004-09-12 10:12 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 17:19 ` Alex Zarochentsev
2004-09-14 2:06 ` William Lee Irwin III
2004-09-14 9:00 ` Roman Zippel
2004-09-14 9:10 ` William Lee Irwin III
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=Pine.LNX.4.61.0409131925100.877@scrub.home \
--to=zippel@linux-m68k.org \
--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=wli@holomorphy.com \
--cc=zam@namesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®