From: Steven Whitehouse <swhiteho@redhat.com>
To: Joel Becker <jlbec@evilplan.org>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
linux-kernel@vger.kernel.org, sunil.mushran@oracle.com
Subject: Re: Cleancache and shared filesystems
Date: Tue, 31 May 2011 09:58:26 +0100 [thread overview]
Message-ID: <1306832306.2816.3.camel@menhir> (raw)
In-Reply-To: <20110527233331.GC30232@noexit.corp.google.com>
Hi,
On Fri, 2011-05-27 at 16:33 -0700, Joel Becker wrote:
> On Fri, May 27, 2011 at 05:19:39PM +0100, Steven Whitehouse wrote:
> > + if (ls->ls_ops == &gfs2_dlm_ops) {
> > + if (gfs2_uuid_valid(sb->s_uuid))
> > + cleancache_init_shared_fs(sb->s_uuid, sb);
> > + } else {
> > + cleancache_init_fs(sb);
> > + }
>
> Hey Dan,
> Steven makes a good point here. ocfs2 could also take advantage
> of local filesystem behavior when running in local mode.
>
> Joel
>
There is a further issue as well - cleancache will only work when all
nodes can see the same shared cache, so we will need a mount option to
disable cleancache in the case we have (for example) a cluster of
virtual machines split over multiple physical hosts.
In fact, I think from the principle of least surprise this had better
default to off and be enabled explicitly. Otherwise I can see that
people will shoot themselves in the foot which will be very easy since
there is no automatic way that I can see to verify that all nodes are
looking at the same cache,
Steve.
next prev parent reply other threads:[~2011-05-31 8:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 13:51 Cleancache and shared filesystems Steven Whitehouse
2011-05-27 15:31 ` Dan Magenheimer
2011-05-27 16:19 ` Steven Whitehouse
2011-05-27 16:31 ` Dan Magenheimer
2011-05-27 23:33 ` Joel Becker
2011-05-31 8:58 ` Steven Whitehouse [this message]
2011-05-31 15:13 ` Dan Magenheimer
2011-05-31 14:51 ` Dan Magenheimer
2011-05-31 21:54 ` Joel Becker
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=1306832306.2816.3.camel@menhir \
--to=swhiteho@redhat.com \
--cc=dan.magenheimer@oracle.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sunil.mushran@oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.