From: Con Kolivas <kernel@kolivas.org>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>,
linux-kernel@vger.kernel.org, Mike Galbraith <efault@gmx.de>
Cc: Nick Sanders <sandersn@btinternet.com>,
Andrew Morton <akpm@osdl.org>,
Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Subject: Re: [PATCH] O3int interactivity for 2.5.74-mm2
Date: Mon, 7 Jul 2003 23:14:18 +1000 [thread overview]
Message-ID: <200307072314.18258.kernel@kolivas.org> (raw)
In-Reply-To: <200307071343.26318.m.c.p@wolk-project.de>
On Mon, 7 Jul 2003 22:19, Marc-Christian Petersen wrote:
> On Monday 07 July 2003 12:51, Nick Sanders wrote:
>
> Hi Con, Hi Andrew,
>
> > > Thanks to Felipe who picked this up I was able to find the one bug
> > > causing me grief. The idle detection code was allowing the sleep_avg to
> > > get to ridiculously high levels. This is corrected in the following
> > > replacement O3int patch. Note this fixes the mozilla issue too. Kick
> > > arse!!
> >
> > Just booted with patch-O3int-0307071315 on top of 2.5.74-mm2 and the
> > mouse stuttering under high CPU load has gone and no audio skipping.
> > Truly brilliant work
> > Thank you
> > Nick
>
> Hmm, this becomes better and better, but it's still not perfect [tm].
Thanks for feedback. I will keep working on it while I still have ideas and
direction based on the feedback.
> - An Xterm needs ~30 seconds to open up while "make -j16 bzImage modules"
> - An Xterm needs ~15 seconds to open up while "make -j8 bzImage modules"
> - XMMS does _not_ skip mp3's while above.
> - Kmail is almost unusable while above (stops for about 5 secs every 15-20
> secs). KMail is also very slow while the machine is doing nothing.
> - X runs with nice 0, prio 15 (nice -11 is prio 4, does not make
> difference)
Noted; and considered the next major hurdle (was also the most notable
complaint from Mike).
Con
next prev parent reply other threads:[~2003-07-07 12:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 17:16 [PATCH] O3int interactivity for 2.5.74-mm2 Con Kolivas
2003-07-06 18:36 ` Felipe Alfaro Solana
2003-07-06 21:14 ` Con Kolivas
2003-07-06 21:17 ` Con Kolivas
2003-07-07 3:19 ` Con Kolivas
2003-07-07 9:13 ` Felipe Alfaro Solana
2003-07-07 9:40 ` Mike Galbraith
2003-07-07 10:25 ` Con Kolivas
2003-07-07 14:06 ` Mike Galbraith
2003-07-07 14:10 ` Con Kolivas
2003-07-07 10:51 ` Nick Sanders
2003-07-07 12:19 ` Marc-Christian Petersen
2003-07-07 13:14 ` Con Kolivas [this message]
2003-07-08 0:31 ` Zwane Mwaikambo
2003-07-09 10:12 ` Marc-Christian Petersen
2003-07-09 10:13 ` Marc-Christian Petersen
2003-07-09 10:22 ` Con Kolivas
2003-07-09 10:23 ` Marc-Christian Petersen
2003-07-09 10:37 ` Con Kolivas
2003-07-09 10:40 ` Marc-Christian Petersen
2003-07-07 13:25 ` Helge Hafting
2003-07-08 6:35 ` Alex Riesen
2003-07-08 7:11 ` Szonyi Calin
2003-07-08 7:46 ` Davide Libenzi
2003-07-08 7:59 ` Con Kolivas
2003-07-08 15:12 ` Davide Libenzi
2003-07-08 20:54 ` Con Kolivas
2003-07-08 20:55 ` Davide Libenzi
2003-07-08 8:03 ` Con Kolivas
2003-07-10 16:27 ` Szonyi Calin
-- strict thread matches above, loose matches on Subject: below --
2003-07-09 15:08 Luis Miguel Garcia
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=200307072314.18258.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=efault@gmx.de \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=sandersn@btinternet.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