From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: ocfs2-devel@oss.oracle.com, Joel Becker <jlbec@evilplan.org>,
Sunil Mushran <sunil.mushran@oracle.com>,
linux-kernel@vger.kernel.org
Subject: RE: bug in cleancache ocfs2 hook, anybody want to try cleancache?
Date: Fri, 3 Jun 2011 08:17:01 -0700 (PDT) [thread overview]
Message-ID: <30a1e906-eb9c-45db-8afe-6c4acc51399a@default> (raw)
In-Reply-To: <f1ce7f0e-91a3-479b-aaea-de92929c77e7@default>
> > I'd like to try and understand the design of the existing code before
> I
> > consider anything more advanced such as writing a kvm backend,
>
> OK. I'd be happy to answer any questions on the design
> at any time.
Oops, forgot to add: If you do any experimentation (e.g.
benchmarking), I strongly recommend that you also try
frontswap** at the same time. As of today, frontswap is
now in linux-next.
Dan
** Frontswap is complementary to cleancache. When memory is
plentiful, cleancache essentially stores more clean page
cache pages to avoid disk reads. When memory is scarce and
swapping is imminent or happening, frontswap stores swap
pages in memory to avoid disk writes and reads. Both
zcache and Xen tmem support both, and in both zcache and
Xen tmem, cleancache pages are prioritized lower than
frontswap pages, i.e. the number of cleancache pages is
reduced as frontswap pages increase. Both cleancache
and frontswap share the underlying Transcendent Memory
"ABI".
next prev parent reply other threads:[~2011-06-03 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 22:45 bug in cleancache ocfs2 hook, anybody want to try cleancache? Dan Magenheimer
2011-06-02 8:45 ` 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 [this message]
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=30a1e906-eb9c-45db-8afe-6c4acc51399a@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