From: Wei Liu <wei.liu2@citrix.com>
To: Maryam Masoudian <maryammasoudian@gmail.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen Memory de-duplication
Date: Sun, 17 Apr 2016 15:20:26 +0100 [thread overview]
Message-ID: <20160417142026.GA27575@citrix.com> (raw)
In-Reply-To: <CAOJrJTfj=73=shvJfzQvXZPD=nui351+Sn=S7sqzwfB4NJzdWQ@mail.gmail.com>
Please don't top post.
On Sun, Apr 17, 2016 at 06:28:15PM +0430, Maryam Masoudian wrote:
> Well, yes memshr is at tools/memshr .
> Then , after modifying this c file, should I compile Xen from scratch?
No, you only need to compile the tools -- or, just that tool.
> And is the sharing feature enabled by default in Xen 4.6 ? If not, how to
> enable it?
>
The hypervisor code is compiled in by default on x86_64 in 4.6.
Wei.
>
> On Sun, Apr 17, 2016 at 4:45 PM, Wei Liu <wei.liu2@citrix.com> wrote:
>
> > On Sun, Apr 17, 2016 at 03:55:00PM +0430, Maryam Masoudian wrote:
> > > Hi,
> > >
> > > I have some questions about memory de-duplication in xen.
> > > Firstly, I want to know if this feature is available in Xen .
> > > If it is, how can I enable it in Xen 4.6 HVM mode.
> > >
> > > Also, if I want to do some logging or other action whenever a COW happens
> > > on shared memory, where should I add my codes? (is the /xen/memshr folder
> > > containing the memory de-duplication code)?
> > >
> >
> > I don't seem to find xen/memshr, only tools/memshr -- that's the tool
> > for manipulating memory sharing. You might want to look into hypervsior
> > code arch/x86/mm/mem_sharing.c.
> >
> > Note that memory sharing is not actively maintained so you might
> > encounter all sorts of problems and on your own to solve them.
> >
> > Wei.
> >
> > > Regards,
> >
>
>
>
> >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xen.org
> > > http://lists.xen.org/xen-devel
> >
> >
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-17 14:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 11:25 Xen Memory de-duplication Maryam Masoudian
2016-04-17 12:15 ` Wei Liu
2016-04-17 13:58 ` Maryam Masoudian
2016-04-17 14:20 ` Wei Liu [this message]
[not found] ` <CAOJrJTc5dynTwiMrtE4Logpz1_ct3oM9vz3HWh1s1sDMY+hSxw@mail.gmail.com>
2016-04-20 13:24 ` Wei Liu
2016-04-20 16:25 ` Tamas K Lengyel
2016-04-20 18:34 ` Dario Faggioli
2016-04-20 19:01 ` Tamas K Lengyel
2016-04-21 12:47 ` Dario Faggioli
[not found] ` <CAOJrJTeK3ntGGwyAjY25xL0g8AXtDcoUOcipF4jmZDCfbdA9Kw@mail.gmail.com>
2016-04-21 15:24 ` Tamas K Lengyel
-- strict thread matches above, loose matches on Subject: below --
2010-10-09 17:56 Xen Memory De-duplication Aditya Gadre
2010-10-09 19:09 ` Pasi Kärkkäinen
2010-10-09 23:40 ` Dan Magenheimer
2010-10-10 5:24 ` Aditya Gadre
2010-10-10 12:34 ` Pasi Kärkkäinen
2010-10-11 7:58 ` Shriram Rajagopalan
2010-10-12 10:20 ` Thomas Goirand
2010-10-12 10:33 ` Tim Deegan
2010-10-11 12:59 ` Tim Deegan
2010-10-08 19:01 Aditya Gadre
2010-10-08 19:02 ` Aditya Gadre
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=20160417142026.GA27575@citrix.com \
--to=wei.liu2@citrix.com \
--cc=maryammasoudian@gmail.com \
--cc=xen-devel@lists.xen.org \
/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).