From: Jan Kara Subject: Re: help with understanding evict inode functionality Date: Thu, 15 Oct 2015 11:53:56 +0200 Message-ID: <20151015095356.GA7173@quack.suse.cz> References: <560E8D36.7010803@paragon-software.com> <788B0E19-4D87-4221-BB69-408E930A0227@netapp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Leonid Fedorenchik , "linux-fsdevel@vger.kernel.org" To: "Kornievskaia, Olga" Return-path: Received: from mx2.suse.de ([195.135.220.15]:35679 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752008AbbJOJx7 (ORCPT ); Thu, 15 Oct 2015 05:53:59 -0400 Content-Disposition: inline In-Reply-To: <788B0E19-4D87-4221-BB69-408E930A0227@netapp.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri 02-10-15 14:38:49, Kornievskaia, Olga wrote: > >>=20 > >> Also can somebody suggest how to debug VFS code, as putting printk= s > >> generates output for the local filesystem code as well. > > You can call printk() only if current process is "nfsd" (at least, > > that is what we did). >=20 > Thanks for the suggestion. I=E2=80=99ll try that. >=20 > Again a general question to the community about inodes and eviction. = I > was under the general impression that when the file is closed the ino= de > sticks around just in case the file is reopened again. Then when > resources are constrainted some background thread evicts unused inode= s. > Is that understanding correct? In that case what is that background > process name?=20 Yes, your understanding is correct. Generally, slab caches (and thus un= used inodes) get reclaimed from kswapd processes. It can happen though, that they are reclaimed basically from any process doing memory allocation w= hen there is shortage of free memory (this is called direct reclaim). Honza --=20 Jan Kara SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html