From: Mariella Petrini <mariellapetrini@yahoo.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com, dgc@sgi.com
Subject: Re: xfs and Linux Linux 2.6.22 and Memory
Date: Thu, 20 Sep 2007 19:14:23 -0700 (PDT) [thread overview]
Message-ID: <773373.46803.qm@web35703.mail.mud.yahoo.com> (raw)
In-Reply-To: <46F2E001.4040107@sandeen.net>
>
> Are you actually seeing a problem with this (caching
> is generally good)
> or just curious?
>
I was mostly curious, especially because In some cases
after having created all the files I may not need to
have all of them cached and I may need to availability
of the RAM for other purposes.
Thank you all for all the info,
Mariella
--- Eric Sandeen <sandeen@sandeen.net> wrote:
> 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
>
>
>
____________________________________________________________________________________
Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545469
next prev parent reply other threads:[~2007-09-21 2:14 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
2007-09-20 23:34 ` David Chinner
2007-09-21 2:14 ` Mariella Petrini [this message]
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=773373.46803.qm@web35703.mail.mud.yahoo.com \
--to=mariellapetrini@yahoo.com \
--cc=dgc@sgi.com \
--cc=sandeen@sandeen.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox