From: Theodore Ts'o <tytso@mit.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Kornievskaia, Olga" <Olga.Kornievskaia@netapp.com>,
Leonid Fedorenchik <leonid.fedorenchik@paragon-software.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: help with understanding evict inode functionality
Date: Sun, 4 Oct 2015 18:37:01 -0400 [thread overview]
Message-ID: <20151004223701.GC4442@thunk.org> (raw)
In-Reply-To: <20151004060136.GA19017@infradead.org>
On Sat, Oct 03, 2015 at 11:01:36PM -0700, Christoph Hellwig wrote:
>
> That's not true. Evict is called when we want to remove an inode
> from memory. i_count needs to be zero for that, but i_nlink doesn't
> as we don't cache inodes forever. When we drop i_count and it reaches
> zero iput_final() is called, which decides depending on ->drop_inode
> to either evict the inode or keep it on the LRU.
Sorry, of course Cristoph is absolutely correct.
- Ted
next prev parent reply other threads:[~2015-10-04 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 13:57 help with understanding evict inode functionality Leonid Fedorenchik
2015-10-02 14:38 ` Kornievskaia, Olga
2015-10-04 2:28 ` Theodore Ts'o
2015-10-04 6:01 ` Christoph Hellwig
2015-10-04 22:37 ` Theodore Ts'o [this message]
2015-10-15 9:53 ` Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2015-10-01 22:54 Kornievskaia, Olga
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=20151004223701.GC4442@thunk.org \
--to=tytso@mit.edu \
--cc=Olga.Kornievskaia@netapp.com \
--cc=hch@infradead.org \
--cc=leonid.fedorenchik@paragon-software.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).