From: Stephan von Krawczynski <skraw@ithnet.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Memory Problem in 2.4.9 ?
Date: Wed, 22 Aug 2001 13:52:07 +0200 [thread overview]
Message-ID: <20010822135207.4e0250b2.skraw@ithnet.com> (raw)
In-Reply-To: <20010821190414Z16086-32384+294@humbolt.nl.linux.org>
In-Reply-To: <20010821154617.4671f85d.skraw@ithnet.com> <20010821174918Z16114-32383+718@humbolt.nl.linux.org> <20010821201733.40fae5cf.skraw@ithnet.com> <20010821190414Z16086-32384+294@humbolt.nl.linux.org>
On Tue, 21 Aug 2001 21:10:44 +0200
Daniel Phillips <phillips@bonn-fries.net> wrote:
> Do you have the same problem on 2.4.8, but not in 2.4.7?
I tested the situation with 2.4.7 (straight, no patches) and it looks like this:
meminfo before:
total: used: free: shared: buffers: cached:
Mem: 921735168 88141824 833593344 0 6643712 36012032
Swap: 271392768 0 271392768
MemTotal: 900132 kB
MemFree: 814056 kB
MemShared: 0 kB
Buffers: 6488 kB
Cached: 35168 kB
SwapCached: 0 kB
Active: 34920 kB
Inact_dirty: 6736 kB
Inact_clean: 0 kB
Inact_target: 864 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 900132 kB
LowFree: 814056 kB
SwapTotal: 265032 kB
SwapFree: 265032 kB
meminfo after test:
total: used: free: shared: buffers: cached:
Mem: 921735168 917393408 4341760 0 221192192 567046144
Swap: 271392768 0 271392768
MemTotal: 900132 kB
MemFree: 4240 kB
MemShared: 0 kB
Buffers: 216008 kB
Cached: 553756 kB
SwapCached: 0 kB
Active: 107912 kB
Inact_dirty: 658432 kB
Inact_clean: 3420 kB
Inact_target: 11360 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 900132 kB
LowFree: 4240 kB
SwapTotal: 265032 kB
SwapFree: 265032 kB
I can see these:
Aug 22 13:34:53 admin kernel: __alloc_pages: 2-order allocation failed.
Aug 22 13:34:53 admin kernel: __alloc_pages: 3-order allocation failed.
Aug 22 13:34:53 admin last message repeated 21 times
_BUT_ I cannot see any errors during NFS-filecopy. I tried hard, but no errors. Another thing is the CPU load. It is definitely lower than with 2.4.9 around 3 - 3.5, but never 4 or above.
Swap is not used, although turned on.
Besides the above kernel-messages I would say that 2.4.7 performs a lot better (and more stable) than 2.4.9 in this test case.
I think a deep look should be taken into this topic, because it makes 2.4.9 pretty unusable for server-environment. I wonder if anybody can produce (low-memory) errors during normal file-operation on localhost (not NFS like me). I would expect that, for it doesn't look NFS specific. I can make the kernel shoot loads of error messages only by reading CDs while copying in the background from the net. The effect can be seen vice versa, too. So you could say it is clearly a memory management problem, and not related to the allocating process.
Should I try with a plain 2.4.8 ?
Regards, Stephan
next prev parent reply other threads:[~2001-08-22 11:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 13:46 Memory Problem in 2.4.9 ? Stephan von Krawczynski
2001-08-21 14:33 ` Daniel Phillips
[not found] ` <20010821194140.43b46b10.skraw@ithnet.com>
[not found] ` <20010821174918Z16114-32383+718@humbolt.nl.linux.org>
2001-08-21 18:17 ` Stephan von Krawczynski
2001-08-21 19:10 ` Daniel Phillips
2001-08-22 0:04 ` Stephan von Krawczynski
2001-08-22 0:43 ` Daniel Phillips
2001-08-22 0:48 ` Rik van Riel
2001-08-22 1:13 ` Daniel Phillips
2001-08-22 10:43 ` Stephan von Krawczynski
[not found] ` <Pine.LNX.4.33.0108220729380.280-100000@mikeg.weiden.de>
2001-08-22 11:01 ` Stephan von Krawczynski
2001-08-22 17:22 ` Mike Galbraith
2001-08-22 19:18 ` Stephan von Krawczynski
2001-08-23 4:57 ` Mike Galbraith
2001-08-22 11:52 ` Stephan von Krawczynski [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-22 4:47 Tommy Wu
2001-08-22 19:32 ` Daniel Phillips
2001-08-22 19:05 ` Marcelo Tosatti
2001-08-23 1:11 ` Daniel Phillips
2001-08-23 0:10 ` Marcelo Tosatti
2001-08-23 2:29 ` Daniel Phillips
2001-08-23 1:19 ` Marcelo Tosatti
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=20010822135207.4e0250b2.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.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