From: Nick Piggin <piggin@cyberone.com.au>
To: Tony Jones <sir_tez@softhome.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test4-mm5 and Warcraft III - WineX
Date: Wed, 10 Sep 2003 15:07:32 +1000 [thread overview]
Message-ID: <3F5EB194.2020102@cyberone.com.au> (raw)
In-Reply-To: <1063169563.21739.1.camel@thelight.sir-tez.org>
Tony Jones wrote:
>In my testing of recent kernels 2.6.0-test5 and 2.6.0-test4-mm4 (mm6
>wouldn't cooperate with X for some reason and I didn't do much
>investigation) I've experied an easily replicable and highly annoying
>problem with Warcraft III and WineX 3.1 (prebuilt).
>
>After playing 1 or 2 games, or leaving the game idle in the chat room,
>the sound will eventually start to stutter and chop badly. In the
>presence of this incredibly bad sound, the mouse and game respond just
>fine (kudos to the scheduler on that point). Considering the game is
>played in "real-time" and is full of audio cues I hate to imagine that
>Con's scheduler will be the "official" scheduler of 2.6 without having
>this issue addressed.
>
>The kernels I use are tainted with nvidia's video drivers, 1.0.4496.
>
>Nick's scheduler in 2.6.0-test4-mm5 seems to be the only thing capable
>of correcting this problem. In general operation, mm5's scheduler
>seems better at handling about everything I threw at it, with a rare
>xmms skip once in a week of use.
>
>I'm not a developer but I'd love some feedback and or questions to
>help figure out why this happens with Con's scheduler patches in mm4
>and test5 to help improve 2.6.0 altogether.
>
Actually, I'd love some feedback from you.
Use this: http://www.kerneltrap.org/~npiggin/v14/sched-rollup-v14.gz
It will apply against 2.6.0-test4 or test5 (not mm). See how you go.
Thanks
prev parent reply other threads:[~2003-09-10 5:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 4:52 2.6.0-test4-mm5 and Warcraft III - WineX Tony Jones
2003-09-10 5:01 ` Tony Jones
2003-09-10 5:15 ` Sipos Ferenc
2003-09-10 5:07 ` Nick Piggin [this message]
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=3F5EB194.2020102@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sir_tez@softhome.net \
/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