From: John M Flinchbaugh <glynis@butterfly.hjsoft.com>
To: linux-kernel@vger.kernel.org
Subject: 2.5.67 scheduling still erratic
Date: Wed, 09 Apr 2003 18:21:27 -0400 [thread overview]
Message-ID: <20030409222126.GA4402@butterfly.hjsoft.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
the cpu starvation issues seem to have cleared a little, but i'm still
seeing issues.
everytime a larger process wakes up, like java gc (jboss) or xfree86
server (especially while switching desktops), mpg123 and/or esd's
audio output gets interrupted and pops. vmstat shows no swapping,
just spikes in user cpu. while rapidly switching desktops, audio can
be delayed for seconds at a time, interrupt count drops slightly (i
guess since no audio), and context switches can double.
are there proc knobs to adjust to alleviate this?
--
____________________}John Flinchbaugh{______________________
| glynis@hjsoft.com http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-04-09 22:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030409222126.GA4402@butterfly.hjsoft.com \
--to=glynis@butterfly.hjsoft.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox