From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
linux-mips@oss.sgi.com, linux-mips@fnet.fr
Subject: Re: ll/sc emulation patch
Date: Thu, 19 Jul 2001 02:18:19 +0200 [thread overview]
Message-ID: <20010719021819.D1888@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1010716133926.12988B-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Mon, Jul 16, 2001 at 02:03:30PM +0200
On Mon, Jul 16, 2001 at 02:03:30PM +0200, Maciej W. Rozycki wrote:
> I didn't profile it very extensively, yet when stracing `ls /usr/lib'
> (fileutils 4.1 linked against glibc 2.2.3) on my system once I yielded
> ~4500 syscalls of which ~4000 were _test_and_set() (or MIPS_ATOMIC_SET,
> depending on my kernel/glibc configuration) invocations. Yes, libpthread
> appears to assume atomic operations are cheap, which is justifiable as
> they are indeed, for almost every other CPU type.
On a fast Indy those 4000 syscalls would cost about 3.2ms of CPU which is
a noticable fraction of the total execution time.
> Also I feel having ll and sc opcodes in a pure MIPS I binary is somewhat
> ugly (e.g. `objdump' won't disassemble them unless a MIPS II+ CPU is
> specified), but I could probably live with it if performance was not
> worse.
This behaviour of objdump sucks rocks anyway. There are MIPS I CPUs which
have ll but no branch likely and many other MIPS ISA perversions. Objdump
also will only hexdump anything that hasn't been marked as code with
.type. Seems objdump's behaviour was choosen to be the most annoying
possible.
Ralf
next prev parent reply other threads:[~2001-07-19 9:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 18:37 ll/sc emulation patch Jan-Benedict Glaw
2001-07-12 20:45 ` Ralf Baechle
2001-07-13 10:52 ` Maciej W. Rozycki
2001-07-14 10:53 ` Ralf Baechle
2001-07-14 17:19 ` Harald Koerfgen
2001-07-16 4:32 ` Jun Sun
2001-07-16 4:51 ` Ralf Baechle
2001-07-16 12:04 ` Maciej W. Rozycki
2001-07-16 10:03 ` Florian Lohoff
2001-07-16 12:03 ` Maciej W. Rozycki
2001-07-16 18:47 ` Mike McDonald
2001-07-16 18:50 ` H . J . Lu
2001-07-16 19:51 ` Maciej W. Rozycki
2001-07-16 20:09 ` H . J . Lu
2001-07-16 20:33 ` Maciej W. Rozycki
2001-07-16 20:43 ` H . J . Lu
2001-07-16 19:12 ` Mike McDonald
2001-07-16 19:40 ` Maciej W. Rozycki
2001-07-19 0:18 ` Ralf Baechle [this message]
2001-07-19 12:56 ` Maciej W. Rozycki
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=20010719021819.D1888@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=jbglaw@lug-owl.de \
--cc=linux-mips@fnet.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox