From: Voluspa <lista1@telia.com>
To: linux-kernel@vger.kernel.org
Cc: kernel@kolivas.org
Subject: Re: WINE + Galciv + 2.6.0-test3-mm1-O15
Date: Wed, 13 Aug 2003 02:54:28 +0200 [thread overview]
Message-ID: <20030813025428.3569ffbc.lista1@telia.com> (raw)
In-Reply-To: <200308130715.23046.kernel@kolivas.org>
On Wed, 13 Aug 2003 07:15:22 +1000
Con Kolivas wrote:
> On Wed, 13 Aug 2003 01:23, Voluspa wrote:
> > On 2003-08-12 14:42:02 gaxt wrote:
> > Similar experience here running the game-test (xfree86 4.3.99.10,
> > winex 3.1 and "Baldurs Gate I") on a PII 400 with 128 meg ram. Using
> > 2.6.0-test3-O14.1int + O14.1-O15int.
>
> Yes known issue for reason I mentioned. Currently investigating.
Yupp, you posted while I was writing.
> > I would say this is the best _and_ worst scheduler I've tried since
> > Con
>
> Can you give us some idea what your machine is like when it's not
> running a cpu hog win32 game in wine? Also can you try running your
> game nice +1
As I've said, it is extremely hard for me to notice the scheduler unless
I run something graphic intensive, but my comments are of course not
solely based on that game-test. A general feel of smoothness can always
be attributed to the placebo effect, though I challenge anyone to
dispute the following experience.
Fourteen days ago I took home a precompiled Blender 2.28 - previous
copy of this 3D render program to reside here was 2.23. Grabbing the
grid which constitutes the world plane (hold third mouse button, drag)
and rotating it around the axes, I noticed something not present in the
old version. Jerks...
In kernel time this is 2.6.0-test1/2 and Cons O11int. Since then I've
done the "world rotate" on plain kernels and all O-patches without
noticing any improvement. Either mouse pointer or grid gets stuck for
about 1/2 to 2 seconds, making the movement unsynchronized. Can happen
while moving slowly, or spinning like crazy.
I don't have DRI with my mach64 (8 meg) because of choice, use Xv
instead, so I had made up my mind about the blame. Sloppy programming
and weak CPU.
Until O15int enters the mix. Perfect sync all the time, no matter how
slow, fast or long I rotate the world plane. That is why I call this
scheduler the "best". The "worst" part comes from the "known issue" but
also because I happened to run xmms on a directory of mp3s while
rotating. I got severe blackouts in the music, ca 10 - 15 seconds long.
When the blackout starts I no longer have to move the mouse, it is
enough to hold down the button. The second I release it, the music
returns.
Xmms has not been involved in the rotating before, so can't tell if the
blackouts have occurred. Could be due to the "known issue", but I'll
retest with older kernels when time permits.
Running the game-test with nice +1... Well, I tried that first on
wineserver, then wine, then X, after which I put -1 on them
consecutively. No real pattern emerged. Badness all around. And now I'm
falling asleep. Bye.
Mvh
Mats Johannesson
next prev parent reply other threads:[~2003-08-13 0:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 15:23 WINE + Galciv + 2.6.0-test3-mm1-O15 Voluspa
2003-08-12 21:15 ` Con Kolivas
2003-08-13 0:54 ` Voluspa [this message]
2003-08-13 18:45 ` Timothy Miller
2003-08-13 21:21 ` Con Kolivas
-- strict thread matches above, loose matches on Subject: below --
2003-07-26 21:49 WINE + Galciv + Con Kolivar's 09 patch to 2.6.0-test1-mm2 gaxt
2003-07-29 3:25 ` Con Kolivas
2003-07-29 12:48 ` WINE + Galciv + Con Kolivas's 011 patch to 2.6.0-test2 gaxt
2003-07-29 12:46 ` Con Kolivas
2003-08-12 14:42 ` WINE + Galciv + 2.6.0-test3-mm1-O15 gaxt
2003-08-12 14:40 ` Con Kolivas
2003-08-12 18:24 ` Mike Galbraith
2003-08-12 18:44 ` Timothy Miller
2003-08-12 18:48 ` Mike Galbraith
2003-08-13 3:34 ` Con Kolivas
2003-08-13 12:47 ` Mike Galbraith
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=20030813025428.3569ffbc.lista1@telia.com \
--to=lista1@telia.com \
--cc=kernel@kolivas.org \
--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