public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Voluspa <lista1@telia.com>, linux-kernel@vger.kernel.org
Subject: Re: WINE + Galciv + 2.6.0-test3-mm1-O15
Date: Wed, 13 Aug 2003 07:15:22 +1000	[thread overview]
Message-ID: <200308130715.23046.kernel@kolivas.org> (raw)
In-Reply-To: <20030812172358.5afe0cc1.lista1@telia.com>

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.

> 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

Con


  reply	other threads:[~2003-08-12 21:09 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 [this message]
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=200308130715.23046.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lista1@telia.com \
    /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