From: Con Kolivas <kernel@kolivas.org>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] O11int for interactivity
Date: Wed, 30 Jul 2003 19:38:23 +1000 [thread overview]
Message-ID: <1059557903.3f27920f97d4a@kolivas.org> (raw)
In-Reply-To: <200307301040.38858.m.c.p@wolk-project.de>
Quoting Marc-Christian Petersen <m.c.p@wolk-project.de>:
> On Wednesday 30 July 2003 10:29, Felipe Alfaro Solana wrote:
>
> Hi Felipe,
>
> > I'm running 2.6.0-test2-mm1 + O11int.patch + O11.1int.patch and I must
> > say this is getting damn good! In the past, I've had to tweak scheduler
> > knobs to tune the engine to my taste, but since O10, this is a thing of
> > the past. It's working as smooth as silk...
> > Good work!
> I really really wonder why I don't experience this behaviour. For me, the
> best
> scheduler patch in the past was the one from you. I had a test last night
> with 011.1 and I rebooted into 2.4 back after some hours of testing because
> it is unusable for me under load, and it is no heavy load, it's just for
> example a simple "make -j2 bzImage modules".
>
> What makes me even more wondering is that 2.6.0-test1-wli tree does not suck
>
> at all for interactivity where no scheduler changes were made.
>
> Maybe we need both: VM fixups (we need them anyway!) and O(1) fixups so that
> also my machine will be happy ;)
The obvious question still needs to be asked here. How does vanilla compare to
vanilla +O11.1?
Con
next prev parent reply other threads:[~2003-07-30 9:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 0:38 [PATCH] O11int for interactivity Con Kolivas
2003-07-30 0:55 ` Con Kolivas
2003-07-30 1:08 ` Con Kolivas
2003-07-31 13:55 ` Szonyi Calin
2003-07-31 13:56 ` Con Kolivas
2003-07-31 15:21 ` Måns Rullgård
2003-07-31 21:38 ` William Lee Irwin III
2003-07-31 22:01 ` Robert Love
2003-07-30 8:29 ` Felipe Alfaro Solana
2003-07-30 8:43 ` Marc-Christian Petersen
2003-07-30 9:38 ` Con Kolivas [this message]
2003-07-30 9:45 ` Marc-Christian Petersen
2003-07-30 12:56 ` Felipe Alfaro Solana
2003-07-30 13:14 ` Wade
2003-07-31 21:43 ` William Lee Irwin III
2003-07-31 21:55 ` William Lee Irwin III
2003-08-01 10:44 ` Marc-Christian Petersen
2003-08-02 21:27 ` Marc-Christian Petersen
2003-08-02 22:55 ` William Lee Irwin III
2003-08-02 23:19 ` Marc-Christian Petersen
2003-08-04 19:06 ` Marc-Christian Petersen
2003-08-04 19:53 ` William Lee Irwin III
2003-08-05 0:56 ` Nick Piggin
2003-08-05 2:41 ` William Lee Irwin III
2003-08-05 3:07 ` Nick Piggin
2003-08-05 3:13 ` William Lee Irwin III
2003-08-05 3:23 ` Nick Piggin
2003-08-05 3:31 ` William Lee Irwin III
2003-08-05 3:38 ` Nick Piggin
2003-08-05 4:54 ` Valdis.Kletnieks
2003-08-05 5:02 ` William Lee Irwin III
2003-08-05 5:55 ` Andrew Morton
2003-08-05 7:11 ` Nick Piggin
2003-08-05 17:00 ` Martin Josefsson
2003-07-30 8:41 ` Felipe Alfaro Solana
2003-07-30 9:35 ` Con Kolivas
2003-07-30 15:33 ` Apurva Mehta
2003-07-31 16:58 ` Moritz Muehlenhoff
2003-07-30 10:31 Voluspa
2003-07-30 10:51 ` Con Kolivas
2003-07-30 11:20 ` Eugene Teo
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=1059557903.3f27920f97d4a@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
/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;
as well as URLs for NNTP newsgroup(s).