From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Neil Brown <neilb@suse.de>
Cc: David Chinner <dgc@sgi.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
nfsv4@linux-nfs.org,
Jean noel Cordenner <jean-noel.cordenner@bull.net>
Subject: Re: [patch 0/2] i_version update
Date: Thu, 31 May 2007 08:36:50 -0400 [thread overview]
Message-ID: <1180615010.6696.45.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <18014.4211.68725.44217@notabene.brown>
On Thu, 2007-05-31 at 10:01 +1000, Neil Brown wrote:
> This will provide a change number that normally changes only when the
> file changes and doesn't require any extra storage on disk.
> The change number will change inappropriately only when the inode has
> fallen out of cache and is being reload, which is either after a crash
> (hopefully rare) of when a file hasn't been used for a while, implying
> that it is unlikely that any client has it in cache.
It will also change inappropriately if the server is under heavy load
and needs to reclaim memory by tossing out inodes that are cached and
still in use by the clients. That change will trigger clients to
invalidate their caches and to refetch the data from the server, further
cranking up the load.
Not an ideal solution...
Trond
prev parent reply other threads:[~2007-05-31 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 16:25 [patch 0/2] i_version update Jean noel Cordenner
2007-05-30 0:21 ` David Chinner
2007-05-30 23:32 ` Mingming Cao
2007-05-31 0:33 ` David Chinner
2007-05-31 18:12 ` Mingming Cao
2007-05-31 0:01 ` Neil Brown
2007-05-31 12:36 ` Trond Myklebust [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=1180615010.6696.45.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=dgc@sgi.com \
--cc=jean-noel.cordenner@bull.net \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfsv4@linux-nfs.org \
/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