From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>,
Nick Piggin <piggin@cyberone.com.au>,
Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: 2.6.0-test4-mm5 and below: Wine and XMMS problems
Date: Sun, 7 Sep 2003 12:08:43 +0200 [thread overview]
Message-ID: <20030907100843.GM14436@fs.tum.de> (raw)
In-Reply-To: <20030902231812.03fae13f.akpm@osdl.org>
On Tue, Sep 02, 2003 at 11:18:12PM -0700, Andrew Morton wrote:
>...
> . Dropped out Con's CPU scheduler work, added Nick's. This is to help us
> in evaluating the stability, efficacy and relative performance of Nick's
> work.
>
> We're looking for feedback on the subjective behaviour and on the usual
> server benchmarks please.
>...
Short story:
I'm still using 2.5.72, all of the 2.6.0-test?{,-mm?} kernels have
problems
Long story:
System:
K6-2 @ 500 MHz
128 MB RAM
1 GB swap
Debian unstable
Workload:
XFree86
FVWM
XMMS
Wine running "Master of Orion 2" (a round based space strategy game)
With 2.4 kernels and 2.5.72 everything works fine.
With 2.6.0-test? and 2.6.0-test?-mm? kernels up to 2.6.0-test4-mm4 the
XMMS sound sometimes skips or sounds slow (like when wou manually retard
a record). That's much more awful than skips.
RAM usage is low, even after a "swapoff -a" at about half of my RAM
would be enough.
The problems might be related to the fact that after I start Wine three
wine.bin processes run and each of them tries to get as much CPU time as
possible.
It might be part of the problem that although Wine is the interactive
task a working XMMS is subjectively more important.
With 2.6.0-test4-mm5 these problems don't occur. Instead, Wine feels
slow. I couldn;t test it much since after the first fast mouse movement
the X mouse cursor has lost the mouse cursor of the game (this might be
a bug in Wine, but it doesnt occur with other kernels).
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-09-07 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 6:18 2.6.0-test4-mm5 Andrew Morton
2003-09-03 7:17 ` 2.6.0-test4-mm5 Christian Axelsson
2003-09-03 18:29 ` 2.6.0-test4-mm5 William Lee Irwin III
2003-09-07 10:08 ` Adrian Bunk [this message]
2003-09-07 10:39 ` 2.6.0-test4-mm5 and below: Wine and XMMS problems Nick Piggin
2003-09-08 23:08 ` Adrian Bunk
2003-09-10 22:03 ` Adrian Bunk
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=20030907100843.GM14436@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=piggin@cyberone.com.au \
/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