From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: ocfs2-devel@oss.oracle.com
Cc: Joel Becker <jlbec@evilplan.org>,
Steven Whitehouse <swhiteho@redhat.com>,
Sunil Mushran <sunil.mushran@oracle.com>,
linux-kernel@vger.kernel.org
Subject: bug in cleancache ocfs2 hook, anybody want to try cleancache?
Date: Wed, 1 Jun 2011 15:45:48 -0700 (PDT) [thread overview]
Message-ID: <da833bdb-7f77-4ebb-ad9b-9fae656b75a1@default> (raw)
As Steven Whitehouse points out in this lkml thread:
https://lkml.org/lkml/2011/5/27/221
there is a bug in the ocfs2 hook to cleancache.
The fix is fairly trivial, but I wonder if anyone
in the ocfs2 community might be interested in trying
out cleancache to author and test the fix?
Currently, the only implementation that benefits from
the sharing functionality is on Xen.
So if you know how to (or are interested in learning
how to) bring up multiple ocfs2 cluster nodes sharing
an ocfs2 filesystem on top of Xen and you are interested
in giving cleancache a spin, please let me know. Else
I will probably push the fix myself.
Dan
P.S. Links to cleancache info:
http://www.phoronix.com/scan.php?page=news_item&px=OTQ5Mw
http://lwn.net/Articles/386090/
http://blogs.oracle.com/wim/entry/another_feature_hit_mainline_linux
---
Thanks... for the memory!
I really could use more / my throughput's on the floor
The balloon is flat / my swap disk's fat / I've OOM's in store
Overcommitted so much
(with apologies to Bob Hope)
next reply other threads:[~2011-06-01 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 22:45 Dan Magenheimer [this message]
2011-06-02 8:45 ` bug in cleancache ocfs2 hook, anybody want to try cleancache? Steven Whitehouse
2011-06-02 18:26 ` Dan Magenheimer
2011-06-03 8:43 ` Steven Whitehouse
2011-06-03 15:03 ` Dan Magenheimer
2011-06-03 15:17 ` Dan Magenheimer
2011-07-26 14:54 ` Dan Magenheimer
2011-07-27 8:13 ` Steven Whitehouse
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=da833bdb-7f77-4ebb-ad9b-9fae656b75a1@default \
--to=dan.magenheimer@oracle.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox