From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andrew Morton <akpm@digeo.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
efault@gmx.de
Subject: Re: [patch] sched-2.5.64-D3, more interactivity changes
Date: 18 Mar 2003 23:13:01 -0800 [thread overview]
Message-ID: <1048057981.1209.17.camel@ixodes.goop.org> (raw)
In-Reply-To: <20030318215228.417e0a58.akpm@digeo.com>
On Tue, 2003-03-18 at 21:52, Andrew Morton wrote:
> > Could people, who can reproduce 'audio skips' kind of problems even with
> > BK-curr, give this patch a go?
>
> I do not test for multimedia performance and cannot comment on this.
I'm still getting starvation problems. If I run xmms with the "Goom"
visualizer (with the window large enough that it is CPU-bound), then
type a command into a shell window (say, ps), it will not run the
command until I close or shrink the goom window. xmms itself plays
fine, though sometimes it fails to go to the next track, apparently for
the same reason (ie, it starts the next track when I disable the
visualizer).
Goom is available from http://ios.free.fr/?page=projet&quoi=1. It
installs pretty easily if you have xmms installed.
That said, it does seem to be better than previous schedulers (for
example, 64-mm8). It used to starve xmms so much that I couldn't close
operate the UI to turn off the visualizer.
J
next prev parent reply other threads:[~2003-03-19 7:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 10:21 [patch] sched-2.5.64-D3, more interactivity changes Ingo Molnar
2003-03-17 18:01 ` Martin J. Bligh
2003-03-19 5:52 ` Andrew Morton
2003-03-19 6:31 ` Joshua Kwan
2003-03-19 7:13 ` Jeremy Fitzhardinge [this message]
2003-03-19 8:21 ` Mike Galbraith
2003-03-19 16:37 ` Jeremy Fitzhardinge
2003-03-19 16:51 ` Jim Houston
-- strict thread matches above, loose matches on Subject: below --
2003-03-18 0:28 Sean Estabrooks
2003-03-19 11:30 Felipe Alfaro Solana
2003-03-19 11:40 Felipe Alfaro Solana
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=1048057981.1209.17.camel@ixodes.goop.org \
--to=jeremy@goop.org \
--cc=akpm@digeo.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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