From: Rob Landley <rob@landley.net>
To: Tom Sightler <ttsig@tuxyturvy.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Strange load issues with 2.5.69/70 in both -mm and -bk trees.
Date: Mon, 2 Jun 2003 18:49:34 -0400 [thread overview]
Message-ID: <200306021849.35813.rob@landley.net> (raw)
In-Reply-To: <1054582030.4679.15.camel@iso-8590-lx.zeusinc.com>
On Monday 02 June 2003 15:27, Tom Sightler wrote:
> On Mon, 2003-06-02 at 13:28, Ingo Molnar wrote:
> > to prove this point, could you try and renice wineserver to -10 (as root)
> > - does that fix the latency issues still?
> >
> > (if this doesnt then it could be the foreground process starving yet
> > another process - we have to find out which one.)
>
> Yes, I thought the same thing, and I did just that, but no, it doesn't
> fix the latency issue. This system has very little running, I made sure
> that there were no sound servers such as esd or arts running, nothing.
> Basically, a plain KDE (with artsd disabled), mozilla, and Crossover
> wine plugin. Even though I couldn't see how it would affect anything I
> tried bumping up the priorities of other processes such as mozilla
> itself, X, etc. Nothing fixed the problem except for lowering the
> priority of the wine process.
Back around March there was a discussion of sharing interactivity bonus with
the server an interactive process was waiting for. It was mostly about
XFree86 not getting batch scheduled and making mouse movement unusable so
easily, but this sounds eerily similar...
In this case, it seems like the wine client either isn't accumulating an
interactivity bonus (busy-waiting?), or else it's not transmitting it to the
wine server (going through the network stack)?
I've been a bit out of touch since then (old ISP blew up, then i got busy).
Just resurfacing now. Maybe it's old news, but assuming the patch I'm
thinking of wasn't backed out while I was away, it may be relevant. The
thread about it started here:
http://lists.insecure.org/lists/linux-kernel/2003/Mar/1244.html
> Could this process be starving the kernel itself so that it simply
> doesn't have time to service the sound correctly?
Unlikely. Interrupts don't depend on the scheduler. (Neither did bottom
halves or tasklets. I don't think work queues do either, but I'm a bit
behind...)
Rob
next prev parent reply other threads:[~2003-06-02 22:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 4:23 Strange load issues with 2.5.69/70 in both -mm and -bk trees Tom Sightler
2003-06-01 4:45 ` Andrew Morton
2003-06-01 17:36 ` Tom Sightler
2003-06-01 20:07 ` Andrew Morton
2003-06-02 1:59 ` Tom Sightler
2003-06-02 7:36 ` Ingo Molnar
2003-06-02 13:36 ` Tom Sightler
2003-06-02 15:14 ` Ingo Molnar
2003-06-02 15:24 ` Arjan van de Ven
2003-06-02 15:25 ` Ingo Molnar
2003-06-02 15:32 ` Tom Sightler
2003-06-02 17:28 ` Ingo Molnar
2003-06-02 19:27 ` Tom Sightler
2003-06-02 22:49 ` Rob Landley [this message]
2003-06-04 8:14 ` Mike Galbraith
2003-06-04 15:08 ` Tom Sightler
2003-06-04 15:12 ` Ingo Molnar
2003-06-04 16:00 ` Tom Sightler
2003-06-04 16:05 ` Mike Galbraith
2003-06-02 20:53 ` Andreas Boman
2003-06-02 23:10 ` Valdis.Kletnieks
[not found] <5.2.0.9.2.20030601084615.00ce6e30@pop.gmx.net>
2003-06-01 17:43 ` Tom Sightler
2003-06-02 7:39 ` Ingo Molnar
2003-06-02 14:30 ` Tom Sightler
2003-06-02 15:24 ` Tom Sightler
2003-06-02 15:47 ` Tom Sightler
2003-06-02 15:53 ` William Lee Irwin III
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=200306021849.35813.rob@landley.net \
--to=rob@landley.net \
--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