From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Tony Mantler <nicoya@apia.dhs.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: SMP stall on process creation
Date: Sat, 16 Dec 2000 16:41:20 -0500 [thread overview]
Message-ID: <20001216164119.A19128@drow.them.org> (raw)
In-Reply-To: <v04003a09b6618d780015@[24.70.162.12]>; from nicoya@apia.dhs.org on Sat, Dec 16, 2000 at 03:34:14PM -0600
On Sat, Dec 16, 2000 at 03:34:14PM -0600, Tony Mantler wrote:
> At 3:00 PM -0600 12/16/2000, Daniel Jacobowitz wrote:
> >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
> Just ran this on my 9600/200mp, 2.4.0-test11 (linux-pmac-devel, not
> terribly current). time says:
> 0.84s user 2.63s system 100% cpu 3.466 total
That's kind of upsetting right there :)
If I can figure out how to do profiling I'll try to track this down.
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/
next prev parent reply other threads:[~2000-12-16 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 21:00 SMP stall on process creation Daniel Jacobowitz
2000-12-16 21:34 ` Tony Mantler
2000-12-16 21:41 ` Daniel Jacobowitz [this message]
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=20001216164119.A19128@drow.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=nicoya@apia.dhs.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 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.