From: Ross Biro <ross.biro@gmail.com>
To: David Ashley <dash@xdr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cached memory never gets released
Date: Tue, 29 Jun 2004 21:25:22 -0400 [thread overview]
Message-ID: <8783be6604062918255d594d19@mail.gmail.com> (raw)
In-Reply-To: <200406291618.i5TGIQ8F028141@xdr.com>
On Tue, 29 Jun 2004 09:18:26 -0700, David Ashley <dash@xdr.com> wrote:
>
>
> In the thread this is made clear somewhat, but when I post new
> emails I don't summarize all that is known about the problem.
Sorry, I missed that part of the thread.
It does sounds like you may have a real problem, so the next step I
would do is instrument kswapd to explain why it's not freeing cache
when it's under demand.
The first step is to add something to kernel/sysctrl.c to create a
variable to turn the debugging code on or off.
Then add a bunch of printk's to mm/vmscan.c explaining why every page
is not being freed, but only when the sysctrl variable is set.
Then get the machine into the bad state and turn on the printks.
Run your program that can't allocate memory
Turn off the printks and analyze the logs.
I'll be happy to help you figure out where to put printks and go over
the logs, but you have to make sure you are really getting an OOM kill
with that much cache for the output to be useful.
next prev parent reply other threads:[~2004-06-30 1:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 16:18 Cached memory never gets released David Ashley
2004-06-30 1:25 ` Ross Biro [this message]
-- strict thread matches above, loose matches on Subject: below --
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 18:35 David Ashley
2004-06-23 18:44 ` Doug McNaught
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=8783be6604062918255d594d19@mail.gmail.com \
--to=ross.biro@gmail.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox