From: "H. J. Lu" <hjl@lucon.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ulrich Drepper <drepper@redhat.com>,
linux-mips@oss.sgi.com,
GNU C Library <libc-alpha@sources.redhat.com>
Subject: Re: PATCH: Always use ll/sc for mips
Date: Wed, 17 Jul 2002 08:01:57 -0700 [thread overview]
Message-ID: <20020717080157.B10247@lucon.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1020717095946.13355C-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Wed, Jul 17, 2002 at 10:31:13AM +0200
On Wed, Jul 17, 2002 at 10:31:13AM +0200, Maciej W. Rozycki wrote:
> On Tue, 16 Jul 2002, H. J. Lu wrote:
>
> > > It sucks performance-wise with no visible gain, so I don't think it is
> > > really desireable. Since the no-ll/sc case is handled correctly, I see no
> >
> > Only <sys/tas.h> is covered by the kernel interface. But it doesn't
> > cover atomicity.h in glibc and libstdc++.
>
> Even if nobody bothered fixing these, that doesn't mean some other code
> is useless. If you don't want to implement these with _test_and_set(),
> then just put equivalent ll/sc code there, which will work thanks to the
> emulation. Depending on the operation it may even be faster than
> _test_and_set() as ll/sc provides a generic way to perform atomic
> operations, while using _test_and_set() might require a spinlock.
>
I am not against reversing the sysdeps/unix/sysv/linux/mips/sys/tas.h
change. But I am not so excited about it to do it myself.
H.J.
prev parent reply other threads:[~2002-07-17 14:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-02 18:40 PATCH: Always use ll/sc for mips H. J. Lu
2002-07-02 20:06 ` Ralf Baechle
2002-07-02 21:04 ` H. J. Lu
2002-07-04 8:00 ` Maciej W. Rozycki
2002-07-04 8:47 ` Kevin D. Kissell
2002-07-04 8:47 ` Kevin D. Kissell
2002-07-04 13:57 ` Ralf Baechle
2002-07-04 14:14 ` Hiroyuki Machida
2002-07-08 17:21 ` Jun Sun
2002-07-08 17:34 ` Ralf Baechle
2002-07-16 0:59 ` Ulrich Drepper
2002-07-16 15:22 ` Maciej W. Rozycki
2002-07-16 15:42 ` H. J. Lu
2002-07-17 8:31 ` Maciej W. Rozycki
2002-07-17 15:01 ` H. J. Lu [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=20020717080157.B10247@lucon.org \
--to=hjl@lucon.org \
--cc=drepper@redhat.com \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.