From: Andrew Morton <akpm@digeo.com>
To: Axel Siebenwirth <axel@hh59.org>, Con Kolivas <conman@kolivas.net>
Cc: lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"lse-tech@lists.sourceforge.net" <lse-tech@lists.sourceforge.net>
Subject: Re: 2.5.34-mm4
Date: Sun, 15 Sep 2002 10:41:18 -0700 [thread overview]
Message-ID: <3D84C63E.76526EDE@digeo.com> (raw)
In-Reply-To: <20020915105021.GA444@prester.freenet.de>
Axel Siebenwirth wrote:
>
> Hi Andrew!
>
> On Fri, 13 Sep 2002, Andrew Morton wrote:
>
> > url: http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.34/2.5.34-mm4/
>
> With changing from 2.5.34-mm2 to -mm4 I have experienced some moments of
> quite unresponsive behaviour. For example I am building X which at that
> special moment causes pretty heavy disk load and the system doesn't respond
> at all. I was using X and was not able to switch consoles or move mouse only
> extremely sluggish.
There are large IDE updates in -mm4, and this is consistent with
a disk which isn't doing DMA any more. Could you (and Con) please
double-check with `hdparm -i' and `hdparm -t' that the disk subsystem
is behaving properly?
Yes, it could well be a VM bug, but I wouldn't want to run round in
confused circles all day ;) Thanks.
> I have seen that it used more swap that usual.
2.5 is much more swaphappy than 2.4. I believe that this is actually
correct behaviour for optimum throughput. But it just happens that
people (me included) hate it. We don't notice the improved runtimes
for the pagecache-intensive operations but we do notice the time it
takes to get the xterms working again.
We have not yet sat down and worked out what to do about this.
> total used free shared buffers cached
> Mem: 191096 159340 31756 0 10568 94100
> -/+ buffers/cache: 54672 136424
> Swap: 289160 0 289160
>
> This is how it looks like under normal circumstances and when building X I
> had 20M in swap usage which seemed quite a lot to me. Maybe I'm just wrong.
> Unfortunately I was not able to start vmstat, first because I can't start
> vmstat when system is not responding and second it doesn't work anyway
> because of your changes.
>
Yeah, sorry. The burden of back-compatibility weighed too heavy and
Rik decided that we just have to fix userspace to follow kernel
changes. There will be breakage for a while; updates are at
http://surriel.com/procps/.
Unfortunately, those updates cause odd-but-not-serious things to
happen to Red Hat initscripts. This happens when you install standard
util-linux as well. It is due to the initscripts passing in arguments
which the standard tools do not understand.
--
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/
next prev parent reply other threads:[~2002-09-15 17:25 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 ` Andrew Morton [this message]
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 ` 2.5.34-mm4 Bill Davidsen
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=3D84C63E.76526EDE@digeo.com \
--to=akpm@digeo.com \
--cc=axel@hh59.org \
--cc=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lse-tech@lists.sourceforge.net \
/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