On Fri 02-10-15 14:38:49, Kornievskaia, Olga wrote: > >> > >> Also can somebody suggest how to debug VFS code, as putting printks > >> 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). > > Thanks for the suggestion. I’ll try that. > > Again a general question to the community about inodes and eviction. I > was under the general impression that when the file is closed the inode > sticks around just in case the file is reopened again. Then when > resources are constrainted some background thread evicts unused inodes. > Is that understanding correct? In that case what is that background > process name? Yes, your understanding is correct. Generally, slab caches (and thus unused inodes) get reclaimed from kswapd processes. It can happen though, that they are reclaimed basically from any process doing memory allocation when there is shortage of free memory (this is called direct reclaim). Honza -- Jan Kara <jack@xxxxxxxx> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
