From: Eric Sandeen <sandeen@sandeen.net>
To: Mariella Petrini <mariellapetrini@yahoo.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs and Linux Linux 2.6.22 and Memory
Date: Thu, 20 Sep 2007 16:02:57 -0500 [thread overview]
Message-ID: <46F2E001.4040107@sandeen.net> (raw)
In-Reply-To: <435577.15025.qm@web35711.mail.mud.yahoo.com>
Mariella Petrini wrote:
> QUESTION:
>
> Is there any way to release that amount of memory
> without unmounting the file systems ?
> Is that caused to some caching mechanism ?
> Or could that be caused by something else ?
It's most likely the linux VFS caching the dentries & inodes, and
therefore caching the xfs inodes as well.
cat /proc/sys/fs/dentry-state and /proc/sys/fs/inode-state to see how
many are in memory, how many are active, and the age limit.
slabtop would fairly easily show you how much is in the dentry_cache &
the inode_cache too.
Are you actually seeing a problem with this (caching is generally good)
or just curious?
-Eric
next prev parent reply other threads:[~2007-09-20 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 19:17 xfs and Linux Linux 2.6.22 and Memory Mariella Petrini
2007-09-20 21:02 ` Eric Sandeen [this message]
2007-09-20 23:34 ` David Chinner
2007-09-21 2:14 ` Mariella Petrini
2007-09-21 3:13 ` Jason White
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=46F2E001.4040107@sandeen.net \
--to=sandeen@sandeen.net \
--cc=mariellapetrini@yahoo.com \
--cc=xfs@oss.sgi.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 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.