From: Matthew Wilcox <matthew@wil.cx>
To: Xin Zhao <uszhaoxin@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: How long can an inode structure reside in the inode_cache?
Date: Sat, 10 Jun 2006 06:13:18 -0600 [thread overview]
Message-ID: <20060610121318.GQ1651@parisc-linux.org> (raw)
In-Reply-To: <4ae3c140606091710k7a320f2ex6390d0e01da4de9b@mail.gmail.com>
On Fri, Jun 09, 2006 at 08:10:10PM -0400, Xin Zhao wrote:
> I was wondering how Linux decide to free an inode from the
> inode_cache? If a file is open, an inode structure will be created and
> put into the inode_cache, but when will this inode be free and removed
> from the inode_cache? after this file is closed? If so, this seems to
> be inefficient.
how can you possibly release an inode while the file's still open?
look at all the information stored in the inode, like the length of the
file, last accessed time, not to mention which filesystem the inode
belongs to.
next prev parent reply other threads:[~2006-06-10 12:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 0:10 How long can an inode structure reside in the inode_cache? Xin Zhao
2006-06-10 12:13 ` Matthew Wilcox [this message]
2006-06-10 17:12 ` Xin Zhao
2006-06-10 19:01 ` Jeff Mahoney
2006-06-11 5:21 ` UZAIR LAKHANI
2006-06-11 5:35 ` Neil Brown
2006-06-12 18:20 ` How long can an inode structure reside in the inode_cache? - read the code Bryan Henderson
2006-06-12 23:28 ` Neil Brown
2006-06-13 23:25 ` Nate Diller
2006-07-05 0:41 ` Andrew Morton
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=20060610121318.GQ1651@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=uszhaoxin@gmail.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;
as well as URLs for NNTP newsgroup(s).