From: Con Kolivas <kernel@kolivas.org>
To: gaxt <gaxt@rogers.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: WINE + Galciv + Con Kolivas's 011 patch to 2.6.0-test2
Date: Tue, 29 Jul 2003 22:46:36 +1000 [thread overview]
Message-ID: <200307292246.36808.kernel@kolivas.org> (raw)
In-Reply-To: <3F266D33.4040106@rogers.com>
On Tue, 29 Jul 2003 22:48, gaxt wrote:
> I tried O11. Still chuggy in the AVIs and then locks out input into X. I
> switch to Alt-F1 console and hear the video advance, switch back, it
> pauses, switch to Alt-F1 etc. to get it through the video and then it's
> fine.
>
> Incidentally, I moved my /home to another hard drive last night (same
> 7200 rpms) to get more space. It makes no difference to performance.
> 260-test2-vanilla was quite good and -mm1 and -O11 are chuggy and lock
> out input to X and require switching to virtual console to advance
> through the videos.
>
> If there is some other data I can provide you, let me know.
What top shows as the PRI of all the important processes concerned during all
this would be helpful.
Con
next prev parent reply other threads:[~2003-07-29 12:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 21:49 WINE + Galciv + Con Kolivar's 09 patch to 2.6.0-test1-mm2 gaxt
2003-07-27 2:05 ` Con Kolivas
2003-07-28 5:17 ` 260test2+O10int breaks : " gaxt
2003-07-28 21:40 ` gaxt
2003-07-28 21:39 ` Con Kolivas
2003-07-29 2:30 ` 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 [this message]
2003-07-29 20:59 ` gaxt
2003-07-29 21:09 ` gaxt
2003-07-29 21:13 ` gaxt
2003-08-08 20:04 ` 2.6.0-test2-mm5 + July Wine + Galciv gaxt
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=200307292246.36808.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=gaxt@rogers.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