From: Martin Bogomolni <martinbogo@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: kernel 2.4 inode/dentry cache not clearing on umount?
Date: Wed, 16 Feb 2005 10:10:14 -0800 [thread overview]
Message-ID: <712fce105021610105eca9ca5@mail.gmail.com> (raw)
In-Reply-To: <712fce105021610034a189430@mail.gmail.com>
Also .. David :
Are you saying that, on a system with 256Megs of ram, of which the
kernel is reporting only 3-4Mb free because the inode/dentry caches
are taking up most of the memory, and NO page/swap file....
char *p;
p = (char *) malloc( 64*1024*1024 );
I assure you that under these conditions, the malloc( ) will fail with NULL.
---------------------------------
Now, in the meantime I have discovered that merely unmounting the
filesystem is not enough to clear the dcache and icache.
However, if I unmount the filesystem then run:
cat /dev/hda > /dev/null
This causes the inode/dentry cache to finally shrink and the amount of
available free memory increases back to ~200Mb. However, this
reduction does not immediately take place when the filesystem is
unmounted, and while the filesystem is mounted .. the inode/dentry
cache does not shrink and leaves only 3Mb of available free memory.
next prev parent reply other threads:[~2005-02-16 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 16:28 NTFS - Kernel memory leak in driver for kernel 2.4.28? Martin Bogomolni
2005-02-16 16:55 ` NTFS - Kernel memory leak in driver for kernel 2.4.28 (update) Martin Bogomolni
2005-02-16 17:00 ` NTFS - Kernel memory leak in driver for kernel 2.4.28? linux-os
2005-02-16 17:16 ` Martin Bogomolni
2005-02-16 18:03 ` kernel 2.4 inode/dentry cache not clearing on umount? Martin Bogomolni
2005-02-16 18:10 ` Martin Bogomolni [this message]
2005-02-17 11:40 ` NTFS - Kernel memory leak in driver for kernel 2.4.28? Anton Altaparmakov
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=712fce105021610105eca9ca5@mail.gmail.com \
--to=martinbogo@gmail.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