mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Voluspa <lista1@telia.com>
To: linux-kernel@vger.kernel.org
Subject: Re: WINE + Galciv + 2.6.0-test3-mm1-O15
Date: Tue, 12 Aug 2003 17:23:58 +0200	[thread overview]
Message-ID: <20030812172358.5afe0cc1.lista1@telia.com> (raw)


On 2003-08-12 14:42:02 gaxt wrote:

[...]
> Galciv plays videos quite smoothly but as soon as I run it it will
> freeze the cursor for 12-15 seconds every half-minute or so even
> within the game itself which is turn-based strategy without a lot of
> whizbang stuff. In the past, the videos would stutter but the game
> would not suffer from more than short pauses now and then.

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.

I would say this is the best _and_ worst scheduler I've tried since Con
had to adopt his work to the new Ingo infrastructure. Slightly
smoother than pure A3 unless you manage to trigger badness. Then you (or
I, at least) get exactly 15 seconds of total freezes, mixed with
different periods of normality. And by freezes, I mean total freezes.

I can switch to an already opened text console, but there
a running "top" is dead and it won't take any keystrokes until the
freeze has gone. The only thing not dead is the "sound repeats" that
Daniel Phillips explained in:

http://marc.theaimsgroup.com/?l=linux-kernel&m=105966612027670&w=2

--quote--
To convince yourself of this, note that when DMA refill fails to meet
its deadline you will hear repeats, not skipping, because the DMA
hardware on the sound card has been set up to automatically restart the
DMA each time the buffer expires.  Try running the kernel under kgdb and
breaking to the monitor while sound is playing.
--unquote--

Mvh
Mats Johannesson

             reply	other threads:[~2003-08-12 15:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12 15:23 Voluspa [this message]
2003-08-12 21:15 ` Con Kolivas
2003-08-13  0:54   ` Voluspa
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=20030812172358.5afe0cc1.lista1@telia.com \
    --to=lista1@telia.com \
    --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

Powered by JetHome