From: Joel Becker <jlbec@evilplan.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Steven Whitehouse <swhiteho@redhat.com>,
linux-kernel@vger.kernel.org,
Sunil Mushran <sunil.mushran@oracle.com>
Subject: Re: Cleancache and shared filesystems
Date: Tue, 31 May 2011 14:54:43 -0700 [thread overview]
Message-ID: <20110531215443.GC31742@noexit.corp.google.com> (raw)
In-Reply-To: <790b3e0b-14b6-44da-9f4c-a4315b58e2c5@default>
On Tue, May 31, 2011 at 07:51:36AM -0700, Dan Magenheimer wrote:
> > Hey Dan,
> > Steven makes a good point here. ocfs2 could also take advantage
> > of local filesystem behavior when running in local mode.
>
> I guess the semantics need to be more clearly defined
> (or perhaps changed if the shared-fs community wants),
> but if cleancache_init_shared_fs is called only by
> a single node, cleancache still enables all the same
> functionality** as cleancache_init_fs.
I don't see the ** reference in the footnotes ;-) You're saying
that, for a single caller, you will properly keep the pagecache bits
around in cleancache as you shrink the balloon and give them back when
requested? So an ocfs2 calling cleancache_init_share_fs() in only one
VM will have the same page lifetimes (including life inside cleancache
but not in guest pagecache) as a similar ext3? If so, there are no
changes needed at all.
> I'm not sure I fully understand the semantics of
> local mode though, so please clarify if you think
> I am wrong or misunderstanding your point.
ocfs2 local mode means that it is not a cluster filesystem. The
cluster services are not enabled, and ocfs2 behaves like xfs/extN/btrfs.
Joel
--
"Lately I've been talking in my sleep.
Can't imagine what I'd have to say.
Except my world will be right
When love comes back my way."
http://www.jlbec.org/
jlbec@evilplan.org
prev parent reply other threads:[~2011-05-31 21:54 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
2011-05-31 15:13 ` Dan Magenheimer
2011-05-31 14:51 ` Dan Magenheimer
2011-05-31 21:54 ` Joel Becker [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=20110531215443.GC31742@noexit.corp.google.com \
--to=jlbec@evilplan.org \
--cc=dan.magenheimer@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sunil.mushran@oracle.com \
--cc=swhiteho@redhat.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.