From: Neil Brown <neilb@suse.de>
To: Simon Peter <simon.peter@gmx.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs-utils inode cache patch
Date: Tue, 13 Mar 2007 15:22:11 +1100 [thread overview]
Message-ID: <17910.9971.125407.778285@notabene.brown> (raw)
In-Reply-To: message from Simon Peter on Friday March 9
On Friday March 9, simon.peter@gmx.de wrote:
> Hi Neil,
>
> okay, here's the patch making the kernel cache inode data of exported
> directories forever, thus avoiding unnecessary disk spin-ups when this
> data is looked for. It looks correct, works for me and both Bruce and
> you have been encouraging it. :) Would be great if that could go into
> nfs-utils.
>
> Thanks,
> Simon
Hmmm...
> Content-Type: video/dv;
> name="nfs-utils-1.0.12-cache.dif"
So it was a video/dv file was it?
Ok, I've applied it and added a big comment.
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.
http://neil.brown.name/git?p=nfs-utils;a=commitdiff;h=b1e1c8a05afdbbc3f217ef79c31c3b8ca302f9eb
Thanks,
NeilBrown
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-03-13 4:22 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 [this message]
2007-03-13 11:40 ` Talpey, Thomas
2007-03-13 14:47 ` J. Bruce Fields
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=17910.9971.125407.778285@notabene.brown \
--to=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