From: David Ashley <dash@xdr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Cached memory never gets released
Date: Wed, 23 Jun 2004 11:35:29 -0700 [thread overview]
Message-ID: <200406231835.i5NIZTSJ019899@xdr.com> (raw)
There is some new information that might be useful. The cache memory
lower limit seems to be going up by 1 or 2 megabytes whenever the kernel
kills the XFree86 process:
Jun 23 11:20:16 __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Jun 23 11:20:16 VM: killing process XFree86
Could it be when the kernel kills a process for trying to use up too much
memory, the pages used by the process get left in some locked state so can
never be reused?
This is the sort of behaviour we're seeing, it is very reproduceable.
Note this is kernel 2.4.23.
-Dave
next reply other threads:[~2004-06-23 18:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 18:35 David Ashley [this message]
2004-06-23 18:44 ` Cached memory never gets released Doug McNaught
-- strict thread matches above, loose matches on Subject: below --
2004-06-29 16:18 David Ashley
2004-06-30 1:25 ` Ross Biro
2004-06-29 15:07 David Ashley
2004-06-29 16:00 ` Ross Biro
2004-06-27 3:24 David Ashley
2004-06-24 17:14 David Ashley
2004-06-24 14:48 David Ashley
2004-06-24 15:49 ` Ross Biro
2004-06-23 15:31 David Ashley
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=200406231835.i5NIZTSJ019899@xdr.com \
--to=dash@xdr.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.