From: "kcn" <kcn@263.net>
To: "'Martin J. Bligh'" <mbligh@aracnet.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: kernel freeze
Date: Tue, 5 Nov 2002 15:25:42 +0800 [thread overview]
Message-ID: <002d01c2849c$927faa40$31036fa6@zhoulin> (raw)
In-Reply-To: <3842257604.1036450149@[10.10.2.3]>
> I'll lay you a large bet that lowmem is full of garbage.
> Probably buffer_heads, inodes or PTEs. Output of /proc/meminfo
> and /proc/slabinfo as you approach oblivion would be useful.
> As would a description of the workload that triggers it.
>
> M.
I think it's the reason. But I have to decreased memory from 4G to 2G
because of the complain from my customers, so I can't give you the
/proc/meminfo or /proc/slabinfo now. :(
Why the linux-vm can't manage lowmem correctly? I have seen some
articles talking about the LRU pre zone patch, but why 2.4.19+rmap14a
patch also has this problem?
next prev parent reply other threads:[~2002-11-05 7:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 6:18 kernel freeze kcn
2002-11-05 6:49 ` Martin J. Bligh
2002-11-05 7:25 ` kcn [this message]
2002-11-05 7:50 ` Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2014-03-29 13:03 Joël Krähemann
2001-09-27 22:28 Kernel Freeze Luca Adesso
2001-09-27 22:47 ` Nicholas Knight
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='002d01c2849c$927faa40$31036fa6@zhoulin' \
--to=kcn@263.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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