From: Tim Deegan <tim@xen.org>
To: ???? <zhangzhi2022@hotmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Copy-on write sharing
Date: Fri, 1 Jun 2012 09:32:16 +0100 [thread overview]
Message-ID: <20120601083216.GA77921@ocelot.phlegethon.org> (raw)
In-Reply-To: <BLU147-W3164E67F10FCA98668A999CC0B0@phx.gbl>
Hi,
Please don't drop the list from Cc. I have put it back.
At 09:50 +0000 on 31 May (1338457855), ???? wrote:
> Hi, I just read about the source code (mainly the mem_sharing.c) that
> you mentioned before, but it seemed not like what I was looking for,
> and it doesn't make use of the rbtree for page sharing.
mem_sharing.c is just the mechanism for having two VMs share a page.
The choices of which pages to share are left to the tools. As I said
the in-tree Xen tools don't currently have a good way to select pages to
share (though there are some out-of-tree users).
> I felt that the functionality of this mem_sharing.c file is not like
> the KSM(kernel samepage mechanism), which operates in the KVM(kernel
> virtual machine).
That's right. KVM reuses linux's existing in-kernel mechanism for
finding and sharing suitable pages.
Tim.
prev parent reply other threads:[~2012-06-01 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 8:39 Copy-on write sharing zhangzhi
2012-05-31 9:23 ` Tim Deegan
[not found] ` <BLU147-W3164E67F10FCA98668A999CC0B0@phx.gbl>
2012-06-01 8:32 ` Tim Deegan [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=20120601083216.GA77921@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=zhangzhi2022@hotmail.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;
as well as URLs for NNTP newsgroup(s).