From: sseeger@stellartec.com (Steven Seeger)
To: <linux-kernel@vger.kernel.org>
Subject: 2.4.18-mips buffer cache problem
Date: Tue, 2 Jul 2002 05:20:44 -0700 [thread overview]
Message-ID: <013e01c221c2$e4074950$3501a8c0@wssseeger> (raw)
Hey guys. I've got 2.4.18 running on an NEC Osprey development board here
using the NEC VR4181 processor. The problem I'm having must be arch
specific, however if I knew where in the Kenrel exactly to look on the Linux
side I would stand a better chance of figuring out what's going on.
When I deal with files on either the CF card or /dev/rom, the buffer cache
fills up. That's what's supposed to happen. However, Linux never seems to
free these buffers. Once I've say, cat * > /dev/null in enough directories
the system memory will all be used up and it won't ever free it. If I
unmount the cf card, it frees up a lot of what was buffered up on the card
so it seems the arch specific memory stuff works, but why won't it free it
up otherwise? The files cached from the /dev/rom device (root fs) fills up
memory and never frees. I have another working kernel that doesn't have this
problem and I can fill up system memory with cache files and then run a
little program that takes up a ton of memory and that program will keep
running, but it page faults on this new kernel since it can't get the memory
it needs from the cache. I don't see why the OOM won't kill it first,
eitehr.
Can somebody tell me where in the Kernel it says "hey, I'm running low on
memory I should free up some of the memory in the file cache" stuff? If I
know where that happens, I can try troubleshooting the problem. I'm sure
it'll point to some specific mips problem.
Thanks!
Steve
reply other threads:[~2002-07-02 12:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='013e01c221c2$e4074950$3501a8c0@wssseeger' \
--to=sseeger@stellartec.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
all inboxes | Powered by JetHome®