Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr,
	linux-mips@vger.rutgers.edu, aj@suse.de
Subject: Re: pause()
Date: Sun, 2 Apr 2000 02:34:25 +0200	[thread overview]
Message-ID: <20000402023425.B829@uni-koblenz.de> (raw)
In-Reply-To: <20000331195303.B20241@paradigm.rfc822.org>; from flo@rfc822.org on Fri, Mar 31, 2000 at 07:53:03PM +0200

On Fri, Mar 31, 2000 at 07:53:03PM +0200, Florian Lohoff wrote:

> On Fri, Mar 31, 2000 at 03:15:55PM +0200, Ralf Baechle wrote:
> > I just found another brainfart in the libc / kernel interface.  In the
> > believe libc wouldn't use the pause(2) syscall any longer I removed it.
> > This makes a number of programs like screen burn all CPU they can get.
> > I'll provide two fixes, one to libc and a second for the kernel and
> > either one will be sufficient.
> 
> Could this also be the cause of "top" refreshing the screen as fast
> as it can ? I noticed that when i rebuild the debian procps package
> and tried top ... It then consumes the cpu it gets ...

I haven't tried myself but sounds very probable.  The sympthon is that
an strace will show large numbers of pause(2) syscalls which all return
with -ENOSYS as error.

  Ralf

  reply	other threads:[~2000-04-02 10:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20000331151555.A5911@uni-koblenz.de>
2000-03-31 17:53 ` pause() Florian Lohoff
2000-04-02  0:34   ` Ralf Baechle [this message]
2000-04-02 12:22     ` pause() Ralf Baechle
2000-04-02 16:20       ` pause() Florian Lohoff

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=20000402023425.B829@uni-koblenz.de \
    --to=ralf@oss.sgi.com \
    --cc=aj@suse.de \
    --cc=flo@rfc822.org \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@vger.rutgers.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    /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