From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "chen, xiangping" <chen_xiangping@emc.com>
Cc: "'nfs-request@lists.sourceforge.net'"
<nfs-request@lists.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: Questions on NFS client inode management.
Date: 11 Sep 2001 22:21:34 +0200 [thread overview]
Message-ID: <shsk7z5zdf5.fsf@charged.uio.no> (raw)
In-Reply-To: <276737EB1EC5D311AB950090273BEFDD043BC5A2@elway.lss.emc.com>
In-Reply-To: "chen, xiangping"'s message of "Tue, 11 Sep 2001 14:30:18 -0400"
>>>>> " " == 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
next prev parent reply other threads:[~2001-09-11 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-11 18:30 chen, xiangping
2001-09-11 20:21 ` Trond Myklebust [this message]
2001-09-11 21:25 chen, xiangping
2001-09-12 7:50 ` Trond Myklebust
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=shsk7z5zdf5.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=chen_xiangping@emc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs-request@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®