mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Tom Sightler <ttsig@tuxyturvy.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] O16.2int
Date: Mon, 18 Aug 2003 11:21:04 +1000	[thread overview]
Message-ID: <1061169664.3f402a00ae7b6@kolivas.org> (raw)
In-Reply-To: <1061156820.1775.32.camel@iso-8590-lx.zeusinc.com>

Quoting Tom Sightler <ttsig@tuxyturvy.com>:

> Hi Con,

Hi Tom

> 1. -- Wine running Windows Media Player 6.4 works great when running in

Yes a well known problem now (see other threads about wine). Wine doing 
something very cpu intensive exhibits this due to a combination of wine 
breakage brought out by my scheduler tweaks causing priority inversion.

> 2. -- Adobe Acrobat 5.07 for Linux seems to have a very similar issue, a
> large complex document seems to starve out the whole system making the
> system feel locked up for several seconds.

Actually I've profiled acroread and it seems to be more a memory issue than a 
scheduler one per se. Something very inefficient about it's design and it 
behaves much worse as a mozilla plugin than standalone. Give it lots of cpu 
time and it just keeps doing more and more vm work.

> 3. -- It seems I can trigger the same kind of starvation by simply doing
> large selects in a Konsole window.  Selecting a large section of text

> Konsole issue, however, if another application is using a reasonable
> amount of CPU, say a video playing in Wine using ~50% CPU, then it seems
> easy to make this happen.  Once it happens it's very hard to recover,

This is because of wine, not the Konsole which behaves fine, but tips the 
combination of wine and something else over the edge.

I'm working on it. Thanks very much for your report.

Cheers,
Con

  reply	other threads:[~2003-08-18  1:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-17 20:37 Benjamin Weber
2003-08-17 21:47 ` Tom Sightler
2003-08-18  1:21   ` Con Kolivas [this message]
2003-08-18 16:51     ` Antonio Vargas
2003-08-18 23:47       ` Con Kolivas
  -- strict thread matches above, loose matches on Subject: below --
2003-08-16 11:07 Voluspa
2003-08-16 14:09 ` Con Kolivas
2003-08-16 14:41   ` Nick Piggin
2003-08-16 15:00     ` Con Kolivas
2003-08-16 14:44   ` Voluspa
2003-08-16  9:02 Con Kolivas
2003-08-16 13:29 ` Wiktor Wodecki
2003-08-17  7:40 ` Andrew Morton
2003-08-17  9:30   ` Con Kolivas
2003-08-17 14:59   ` Con Kolivas
2003-08-17 21:06     ` Andrew Morton

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=1061169664.3f402a00ae7b6@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ttsig@tuxyturvy.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

Powered by JetHome