From: Bill Davidsen <davidsen@tmr.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, lse-tech@lists.sourceforge.net
Subject: Re: 2.5.34-mm4
Date: Mon, 16 Sep 2002 14:48:35 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.1020916143506.6180E-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <3D84D799.557653C7@digeo.com>
On Sun, 15 Sep 2002, Andrew Morton wrote:
> Impressions are:
>
> - 2.5 swaps a lot in response to heavy pagecache activity.
>
> SEGQ didn't change that, actually. And this is correct,
> as-designed behaviour. We'll need some "don't be irritating"
> knob to prevent this. Or speculative pagein when the load
> has subsided, which would be a fair-sized project.
It would be nice to have a knob in /proc/sys which could be tuned for
response or throughput, Preferably not a boolean;-) I suspect that we
would have lack of agreement on what that would do, but it sure would be
nice!
> - In both -ac and 2.5 the scheduler is prone to starving interactive
> applications (netscape 4, gkrellm, command-line gdb, others) when
> there is a compilation happening.
>
> This is very, very noticeable; and it afects applications which
> do not use sched_yield(). Ingo has put some extra stuff in since
> then and I need to retest.
>
> - In -ac, there are noticeable stalls during heavy writeout. This
> may be an ext3 thing, but I can't think of any IO scheduling
> differences in -ac ext3. I'd be guessing that it is due to
> bdflush/kupdate lumpiness.
I have the feeling that 2.5 is less good about noting that a file is open
for write only and no seeks have been done. I haven't measured it, but it
would seem that writes to such a file would be better on the disk and not
taking buffers, since they're probably not going to be read.
This is just based on running mkisofs on 2.4.19 and 2.5.34, a watching "no
disk activity" followed by a heavy burst. I haven't made any careful
measurement, so take this as you will, but I agree that heavy write bogs
the system. Clearly with big memory I can/do get the whole ~700MB in
memory if writes don't start quickly.
Yes, that could be tuning, I know that.
> Overall I find Marcelo kernels to be the most comfortable, followed
> by 2.5. Alan's kernels I find to be the least comfortable in a
> "developer's desktop" situation.
On small memory machines I don't see as much to choose, and the -ck series
has been very nice to me. I don't run 2.5 on any but test machines, and
both are big memory (1+GB) machines.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
prev parent reply other threads:[~2002-09-16 18:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-14 4:06 2.5.34-mm4 Andrew Morton
2002-09-14 4:01 ` 2.5.34-mm4 Rik van Riel
2002-09-15 10:50 ` 2.5.34-mm4 Axel Siebenwirth
2002-09-15 14:31 ` 2.5.34-mm4 Rik van Riel
2002-09-16 18:33 ` 2.5.34-mm4 Bill Davidsen
2002-09-15 17:41 ` 2.5.34-mm4 Andrew Morton
2002-09-15 17:36 ` 2.5.34-mm4 Rik van Riel
2002-09-15 17:39 ` 2.5.34-mm4 Rik van Riel
2002-09-15 17:49 ` 2.5.34-mm4 M. Edward Borasky
2002-09-15 17:54 ` 2.5.34-mm4 Rik van Riel
2002-09-15 18:55 ` 2.5.34-mm4 Andrew Morton
2002-09-15 18:56 ` 2.5.34-mm4 Rik van Riel
2002-09-16 1:33 ` 2.5.34-mm4 Alan Cox
2002-09-16 2:32 ` [PATCH](1/2) rmap14 for ac (was: Re: 2.5.34-mm4) Rik van Riel
2002-09-15 19:10 ` [Lse-tech] Re: 2.5.34-mm4 Andi Kleen
2002-09-16 18:51 ` Bill Davidsen
2002-09-19 9:01 ` Jens Axboe
2002-09-16 18:48 ` Bill Davidsen [this message]
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=Pine.LNX.3.96.1020916143506.6180E-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lse-tech@lists.sourceforge.net \
--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