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: Tue, 26 Jul 2011 07:54:31 -0700 (PDT) [thread overview]
Message-ID: <3904dcad-951e-43ca-bd2d-1c906d0b0a9e@default> (raw)
In-Reply-To: <1307090628.2881.15.camel@menhir>
> > > Also, as regards your earlier question wrt a kvm backend, I may be
> > > tempted to have a go at writing one, but I'd like to figure out what
> > > I'm letting myself in for before making any commitment to that,
>
> > I think the hardest part is updating the tmem.c module in zcache
> > to support multiple "clients". When I ported it from Xen, I tore
> > all that out. Fortunately, I've put it back in during RAMster
> > development but those changes haven't yet seen the light of day
> > (though I can share them offlist).
>
> 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,
FYI, the "hardest part" (support for multiple clients) is now in
Linus's tree as of today. With a little hypercall and glue code,
KVM might just work now with tmem/cleancache/frontswap.
Dan
next prev parent reply other threads:[~2011-07-26 14:55 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
2011-07-26 14:54 ` Dan Magenheimer [this message]
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=3904dcad-951e-43ca-bd2d-1c906d0b0a9e@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