Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: "Abhishek Rai" <abbashake007@yahoo.com>,  <nfs@lists.sourceforge.net>
Subject: Re: regarding size limit of local client cache
Date: 11 Mar 2003 19:37:42 +0100	[thread overview]
Message-ID: <shssmttiwax.fsf@charged.uio.no> (raw)
In-Reply-To: <6440EA1A6AA1D5118C6900902745938E07D5538B@black.eng.netapp.com>

>>>>> " " == Charles Lever <Lever> writes:

     > hi- you didn't tell us how large your client's RAM is, what
     > your mount options are, what other programs are running on the
     > clients, nor how long each client takes to read (attribute
     > cache invalidation might cause each client to purge its cache,
     > for instance).

     > as far as i know there is no 8192 page limit in the NFS client.

Right. The size of the page cache is limited only by the available
free memory.

Cheers,
  Trond


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2003-03-11 18:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11 15:27 regarding size limit of local client cache Lever, Charles
2003-03-11 18:30 ` Abhishek Rai
2003-03-11 18:37 ` Trond Myklebust [this message]
2003-03-11 21:12   ` Abhishek Rai
2003-03-11 22:14     ` Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2003-03-11  7:33 Abhishek Rai

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=shssmttiwax.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=Charles.Lever@netapp.com \
    --cc=abbashake007@yahoo.com \
    --cc=nfs@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