From: Nick Piggin <piggin@cyberone.com.au>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Andrew Morton <akpm@osdl.org>, Con Kolivas <kernel@kolivas.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.0-test4-mm5 and below: Wine and XMMS problems
Date: Sun, 07 Sep 2003 20:39:14 +1000 [thread overview]
Message-ID: <3F5B0AD2.3000706@cyberone.com.au> (raw)
In-Reply-To: <20030907100843.GM14436@fs.tum.de>
Adrian Bunk wrote:
>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
>
Hi Adrian,
It would be great if you could test the latest mm kernel (mm6 as of now
I think), which has Con's latest stuff in it. You could also test my
newest scheduler patch. Thanks for the feedback.
next prev parent reply other threads:[~2003-09-07 10:42 UTC|newest]
Thread overview: 35+ 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-03 16:12 ` 2.6.0-test4-mm5 Adrian Bunk
2003-09-03 16:32 ` [PATCH] 2.6.0-test4-mm5 Jeff Garzik
2003-09-03 16:46 ` Benjamin Herrenschmidt
2003-09-03 23:31 ` Jeff Garzik
2003-09-04 7:29 ` Benjamin Herrenschmidt
2003-09-04 3:21 ` David S. Miller
2003-09-03 17:02 ` 2.6.0-test4-mm5: SCSI imm driver doesn't compile Adrian Bunk
2003-09-04 13:30 ` Arnaldo Carvalho de Melo
2003-09-04 13:52 ` Jan-Benedict Glaw
2003-09-04 14:30 ` Christoph Hellwig
2003-09-04 14:54 ` Jan-Benedict Glaw
2003-09-04 17:50 ` [new patch] " Adrian Bunk
2003-09-03 23:08 ` 2.6.0-test4-mm5 Diego Calleja García
2003-09-04 1:32 ` 2.6.0-test4-mm5 Nick Piggin
2003-09-04 18:23 ` 2.6.0-test4-mm5 Diego Calleja García
2003-09-04 19:08 ` 2.6.0-test4-mm5 Mike Fedyk
2003-09-05 15:36 ` 2.6.0-test4-mm5 Martin Schlemmer
2003-09-05 16:17 ` 2.6.0-test4-mm5 Nick Piggin
2003-09-05 18:05 ` 2.6.0-test4-mm5 Diego Calleja García
2003-09-04 2:04 ` 2.6.0-test4-mm5 Mike Fedyk
2003-09-04 3:10 ` 2.6.0-test4-mm5 Nick Piggin
2003-09-04 1:30 ` 2.6.0-test4-mm5 Bill Huey
2003-09-04 3:12 ` 2.6.0-test4-mm5 Chris Wright
2003-09-04 14:29 ` 2.6.0-test4-mm5 Bruno T. Moura
2003-09-04 14:44 ` 2.6.0-test4-mm5 Bruno T. Moura
2003-09-04 20:29 ` 2.6.0-test4-mm5 Alan Cox
2003-09-07 10:08 ` 2.6.0-test4-mm5 and below: Wine and XMMS problems Adrian Bunk
2003-09-07 10:39 ` Nick Piggin [this message]
2003-09-08 23:08 ` Adrian Bunk
2003-09-10 22:03 ` Adrian Bunk
2003-09-07 12:18 ` Con Kolivas
2003-09-07 19:04 ` 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=3F5B0AD2.3000706@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=bunk@fs.tum.de \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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