From: Con Kolivas <kernel@kolivas.org>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, Mike Galbraith <efault@gmx.de>,
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: Wed, 9 Jul 2003 20:22:07 +1000 [thread overview]
Message-ID: <200307092022.07723.kernel@kolivas.org> (raw)
In-Reply-To: <200307091211.57017.m.c.p@wolk-project.de>
On Wed, 9 Jul 2003 20:12, Marc-Christian Petersen wrote:
> On Tuesday 08 July 2003 02:31, Zwane Mwaikambo wrote:
>
> Hi Zwane,
>
> > > - 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.
> >
> > How fast is your box? RAM? disks? I'm personally more interested in 1-2
> > make -j2 bzImage going
>
> - Celeron 1,3GHz
> - 512MB RAM
> - 1GB SWAP (2 IDE disks, ~512MB on each disk)
> - ATA100 Maxtor 60GB HDD
> - ATA100 Fujitsu 40GB
>
> Now I am running 2.5.74-mm3, xterm needs about 5 seconds to open up, but
> the whole system is again in a snail mode. XMMS does not skip.
Well this is no different to the O3 patch on mm2 so it's no surprise :)
Con
>
> > > - 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)
> >
> > Looking at above load i'm not entirely surprised, but i presume you're
> > going to name a kernel which can handle that and still complete the
> > builds withing a sane time frame.
>
> For example, my wolk4 tree can handle it very well. 2.4-aa can handle it
> very well too.
>
> ciao, Marc
next prev parent reply other threads:[~2003-07-09 10:11 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
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 [this message]
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=200307092022.07723.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 \
--cc=zwane@arm.linux.org.uk \
/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