linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: mru@users.sourceforge.net (Måns Rullgård), linux-kernel@vger.kernel.org
Subject: Re: [PATCH]O18.1int
Date: Mon, 25 Aug 2003 20:48:38 +1000	[thread overview]
Message-ID: <200308252048.38562.kernel@kolivas.org> (raw)
In-Reply-To: <yw1xad9yca8j.fsf@users.sourceforge.net>

On Mon, 25 Aug 2003 20:17, Måns Rullgård wrote:
> Alex Riesen <alexander.riesen@synopsys.COM> writes:
> >> XEmacs still spins after running a background job like make or grep.
> >> It's fine if I reverse patch-O16.2-O16.3. The spinning doesn't happen
> >> as often, or as long time as with O16.3, but it's there and it's
> >> irritating.
> >
> > another example is RXVT (an X terminal emulator). Starts spinnig after
> > it's child has exited. Not always, but annoyingly often. System is
> > almost locked while it spins (calling select).
>
> It sounds like the same bug.  IMHO, it's rather bad, since a
> non-privileged process can make the system unusable for a non-zero
> amount of time.
>
> How should I do to capture some information about this thing?  Do you
> know what causes it, Con?

Read my rfc on the orthogonal interactivity patches and look under priority 
inversion. It may be that, in which case it happens to vanilla as well. To 
capture useful information for me is quite easy. Run a reniced -11 top -d 1 
-b in batch mode and reniced -11 vmstat 1 in batch mode to capture it 
happening. That should be enough information to see what's going on and 
doesn't need a kernel compile or any special tools. Renice -11 to make sure 
the tools dont get preempted in that period.

Con


  parent reply	other threads:[~2003-08-25 10:41 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-23  5:55 [PATCH]O18.1int Con Kolivas
2003-08-23  9:08 ` [PATCH]O18.1int Thomas Schlichter
2003-08-23  9:18   ` [PATCH]O18.1int Nick Piggin
2003-08-23 12:22     ` [PATCH]O18.1int Con Kolivas
2003-08-23 12:21   ` [PATCH]O18.1int Con Kolivas
2003-08-23  9:32 ` [PATCH]O18.1int Andrew Morton
2003-08-23  9:49   ` [PATCH]O18.1int Nick Piggin
2003-08-23 16:58     ` [PATCH]O18.1int Con Kolivas
2003-08-23 21:49       ` [PATCH]O18.1int Andrew Morton
2003-08-24  2:46         ` [PATCH]O18.1int Con Kolivas
2003-08-23 13:29   ` [PATCH]O18.1int Con Kolivas
2003-08-25  9:24 ` [PATCH]O18.1int Måns Rullgård
2003-08-25  9:42   ` [PATCH]O18.1int Alex Riesen
2003-08-25 10:16     ` [PATCH]O18.1int Con Kolivas
2003-08-25 10:21       ` [PATCH]O18.1int Alex Riesen
2003-08-25 21:02         ` [PATCH]O18.1int Alex Riesen
2003-08-25 22:48           ` [PATCH]O18.1int Con Kolivas
2003-08-25 23:00             ` [PATCH]O18.1int Alex Riesen
2003-08-26 22:03         ` [PATCH]O18.1int Alex Riesen
2003-08-25 10:34       ` [PATCH]O18.1int Måns Rullgård
2003-08-25 10:50         ` [PATCH]O18.1int Con Kolivas
2003-08-25 11:15           ` [PATCH]O18.1int Måns Rullgård
2003-08-25 11:37             ` [PATCH]O18.1int Con Kolivas
2003-08-25 11:58               ` [PATCH]O18.1int Måns Rullgård
2003-08-25 12:28                 ` [PATCH]O18.1int Con Kolivas
2003-08-25 12:49                   ` [PATCH]O18.1int Måns Rullgård
2003-08-25 13:32                     ` [PATCH]O18.1int Con Kolivas
2003-08-25 10:17     ` [PATCH]O18.1int Måns Rullgård
2003-08-25 10:34       ` [PATCH]O18.1int Alex Riesen
2003-08-25 11:23         ` [PATCH]O18.1int Måns Rullgård
2003-08-25 10:48       ` Con Kolivas [this message]
     [not found]       ` <3F49E482.7030902@cyberone.com.au>
     [not found]         ` <20030825102933.GA14552@Synopsys.COM>
2003-08-26 22:20           ` [PATCH]O18.1int Alex Riesen
2003-08-27  2:26             ` [PATCH]O18.1int Nick Piggin
2003-08-23 22:03 [PATCH]O18.1int Voluspa
2003-08-24  4:04 ` [PATCH]O18.1int Con Kolivas
2003-08-28 12:23 [PATCH]O18.1int Guillaume Chazarain
2003-08-28 13:43 [PATCH]O18.1int Guillaume Chazarain
2003-08-28 13:58 ` [PATCH]O18.1int Nick Piggin

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=200308252048.38562.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@users.sourceforge.net \
    /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).