Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Mike McDonald <mikemac@mikemac.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	linux-mips@oss.sgi.com, linux-mips@fnet.fr
Subject: Re: ll/sc emulation patch
Date: Mon, 16 Jul 2001 12:12:08 -0700	[thread overview]
Message-ID: <200107161912.MAA09606@saturn.mikemac.com> (raw)
In-Reply-To: Your message of "Mon, 16 Jul 2001 11:47:04 PDT." <200107161847.LAA09164@saturn.mikemac.com>


>To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
>Subject: Re: ll/sc emulation patch 
>Date: Mon, 16 Jul 2001 11:47:04 -0700
>From: Mike McDonald <mikemac@mikemac.com>
>
>
>>Date: Mon, 16 Jul 2001 14:03:30 +0200 (MET DST)
>>From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
>>To: Ralf Baechle <ralf@oss.sgi.com>
>>Subject: Re: ll/sc emulation patch

>> 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. 
>
>  Not knowing anything about the glibc architecture, I have a dumb
>question: why is 'ls' doing anything at all with pthreads?

  OK, let me rephrase this: why are ~90% of ls's syscalls calls to
_test_and_set() when 'ls' is(??) a single threaded program? Does glibc
always assume it's running in a multithreaded environment?

  Mike McDonald
  mikemac@mikemac.com

  parent reply	other threads:[~2001-07-16 19:12 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 [this message]
2001-07-16 19:40           ` Maciej W. Rozycki
2001-07-19  0:18         ` Ralf Baechle
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=200107161912.MAA09606@saturn.mikemac.com \
    --to=mikemac@mikemac.com \
    --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