From: Con Kolivas <conman@kolivas.net>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: linux-kernel@vger.kernel.org, Rik van Riel <riel@conectiva.com.br>
Subject: Re: [PATCH] 2.4.20-rmap15a
Date: Mon, 2 Dec 2002 11:18:41 +1100 [thread overview]
Message-ID: <1038788321.3deaa6e126a0c@kolivas.net> (raw)
In-Reply-To: <200212012236.17431.m.c.p@wolk-project.de>
Quoting Marc-Christian Petersen <m.c.p@wolk-project.de>:
> On Sunday 01 December 2002 22:25, you wrote:
>
> Hi Rik,
>
> > That was my gut feeling as well, but I guess it's a good thing
> > to quantify how much of a difference it makes. I wonder if we
> > could convince Con to test a kernel both with and without this
> > patch and look at the difference.
> yep, would be a good idea. Con: *wake up ;)*
>
> > > So, here my patch proposal. Ontop of 2.4.20-rmap15a.
> > Looks good, now lets test it. If the patch is as needed as you
> > say we should push it to marcelo ;)
> yep, Andrew should do it. Anyway, all those patches do _not_ get rid of those
>
> I/O pauses/stops since 2.4.19-pre6. Andrea did a good approach with his
> lowlatency elevator, even if it drops throughput (needs more testing to
> become equivalent to throughput w/o it) and also Con and me did a Mini
> Lowlatency Elevator + Config option, so you can decide weather you are
> building for serverusage where interactive "desktop performance" is not
> needed ;) or not.
Ok here are the contest results on the SMP machine with the read latency 2 patch
(rl2) and my 3 line disk latency hack (dlh) which almost disables the elevator
on vanilla 2.4.20:
io_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.4.19 [5] 162.3 45 28 19 4.48
2.4.20 [5] 164.9 45 31 21 4.55
2.4.20-dlh [3] 47.3 157 0 1 1.31
2.4.20-rl2 [3] 101.8 76 19 22 2.81
io_other:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.4.19 [5] 62.3 117 11 20 1.72
2.4.20 [5] 89.6 86 17 21 2.47
2.4.20-dlh [3] 45.0 159 0 1 1.24
2.4.20-rl2 [3] 51.8 142 10 21 1.43
Note no mention of throughput here - but implied drop off with dlh! My guess is
the drop in throughput with dlh is much worse during kernel compilation than
when the machine is idle. Nonetheless the dlh hack makes a significant
improvement in responsivenss under IO load on a desktop.
Con
next prev parent reply other threads:[~2002-12-02 0:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-01 20:56 [PATCH] 2.4.20-rmap15a Marc-Christian Petersen
2002-12-01 21:25 ` Rik van Riel
2002-12-01 21:41 ` Marc-Christian Petersen
2002-12-01 21:56 ` Con Kolivas
2002-12-02 0:18 ` Con Kolivas [this message]
2002-12-02 8:15 ` Jens Axboe
2002-12-02 8:51 ` Andrew Morton
2002-12-02 8:56 ` Jens Axboe
2002-12-02 12:38 ` Rik van Riel
2002-12-02 20:45 ` Willy Tarreau
2002-12-02 23:10 ` Rik van Riel
2002-12-03 6:21 ` Willy Tarreau
2002-12-02 21:46 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2002-12-01 20:35 Rik van Riel
2002-12-03 13:55 ` Miquel van Smoorenburg
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=1038788321.3deaa6e126a0c@kolivas.net \
--to=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=riel@conectiva.com.br \
/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