linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: SMP stall on process creation
Date: Sat, 16 Dec 2000 16:00:04 -0500	[thread overview]
Message-ID: <20001216160004.A18814@drow.them.org> (raw)


I've been using a dual G4/500 with the linuxppc_2_5 tree for a couple weeks
now, and having all sorts of strange problems.  While trying to debug one
(console corruption on select, and sometimes on boot), I discovered
something very interesting.

I ran, in zsh, this command:
% time (for i in {1..100}; do /bin/echo -n; done)

on several machines.  On an old 604e/200:
  0.52s user 1.25s system 100% cpu 1.759 total

On a dual-450 celeron system:
  0.15s user 0.18s system 62% cpu 0.530 system

But on the G4:
  0.07s user 6.24s system 100% cpu 6.302 total

This obviously slows shell scripts to a crawl - forking or execing is being
severely penalized.  I'm also a little startled by the 100% cpu - this is a
multiprocessor system, that loop should NOT have been throttling both
processors.

Does anyone have any ideas?  I'm going to go play with 2.2 SMP and 2.4 UP
for comparison.

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-12-16 21:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-16 21:00 Daniel Jacobowitz [this message]
2000-12-16 21:34 ` SMP stall on process creation Tony Mantler
2000-12-16 21:41   ` Daniel Jacobowitz
2000-12-16 23:55 ` Daniel Jacobowitz

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=20001216160004.A18814@drow.them.org \
    --to=dmj+@andrew.cmu.edu \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).