Messages in this thread | | | From | "chen, xiangping" <> | Subject | RE: Questions on NFS client inode management. | Date | Tue, 11 Sep 2001 17:25:46 -0400 |
| |
Hi, Trond
Thanks for the reply. What kind of reclaiming scheme is used by NFS client and the Linux local file system, say ext2/ext3? Is it used for reclaiming the inode resources, or for memory in general (like killing processes)?
Is there any benchmark available to test how many active inodes a particular system can support?
Xiangping
-----Original Message----- From: Trond Myklebust [mailto:trond.myklebust@fys.uio.no] Sent: Tuesday, September 11, 2001 4:22 PM To: chen, xiangping Cc: 'nfs-request@lists.sourceforge.net'; linux-kernel@vger.kernel.org Subject: Re: Questions on NFS client inode management.
>>>>> " " == xiangping chen <chen> writes:
> Hi, I have a question on inode management for NFS client. It > seems that the inodes created on a NFS client for a mounted nfs > file system stays around until the file being removed. Is there > any limits on how many inodes are allowed in memory for NFS? > What kind of behavior we expect if a malicious/careless > application just keeps creating new files and flood the kernel > memory with inodes created?
The same behaviour as for local files: as memory goes low, the ordinary reclaiming schemes kick in, and all should be hunky-dory. Of course in the *real world*, ...
Cheers, Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |