From: "J. Bruce Fields" <bfields@fieldses.org>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net, Simon Peter <simon.peter@gmx.de>
Subject: Re: nfs-utils inode cache patch
Date: Tue, 13 Mar 2007 10:47:14 -0400 [thread overview]
Message-ID: <20070313144714.GF23604@fieldses.org> (raw)
In-Reply-To: <17910.9971.125407.778285@notabene.brown>
On Tue, Mar 13, 2007 at 03:22:11PM +1100, Neil Brown wrote:
> While reflecting I remembered that I like the fact that unused
> information eventually disappeared from the kernel (where memory
> cannot be pages out). This information won't any more.
>
> But that probably isn't a big cost.
The cost of the export structure itself should be very small. I would
have guessed that the it's the mounts that are the bigger problem. But
I think additional work is needed to allow us to keep only currently
used filesystems mounted.
And in any case if Olaf is right then it may not be the cost of keeping
those filesystems mounted so much as the time required to mount them all
at once on startup. So that might be the problem to work on first.
But I wonder how much memory it takes to keep a few thousand mounts?
And in addition to the memory, are there any bits of VFS code that don't
scale well to lots of mounts?
--b.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-03-13 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 17:09 nfs-utils inode cache patch Simon Peter
2007-03-13 4:22 ` Neil Brown
2007-03-13 11:40 ` Talpey, Thomas
2007-03-13 14:47 ` J. Bruce Fields [this message]
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=20070313144714.GF23604@fieldses.org \
--to=bfields@fieldses.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=simon.peter@gmx.de \
/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