Memory de-duplication

Memory de-duplication

[Kaustubh Kabra]

I have gone through the details of tmem and the patch provided by
a group consisting Dan Magenheimer  as,

[Xen-devel] [PATCH] [xen-unstable] tmem: add page deduplication with opt .
http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00148.html

The further details of the project as such are not available . So I
request someone,who is aware of further development, to provide
information about current status of the project.

Re: Memory de-duplication

[Konrad Rzeszutek Wilk]

On Thu, Aug 26, 2010 at 05:31:25PM +0530, Kaustubh Kabra wrote:
> I have gone through the details of tmem and the patch provided by
> a group consisting Dan Magenheimer  as,

Just curious, but why didn't you CC Dan on this e-mail?

> 
> [Xen-devel] [PATCH] [xen-unstable] tmem: add page deduplication with opt .
> http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00148.html
> 
> The further details of the project as such are not available . So I
> request someone,who is aware of further development, to provide
> information about current status of the project.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

RE: Memory de-duplication

[Dan Magenheimer]

Hello Kaustubh --

I'm sorry I didn't reply to your earlier direct email.

Tmem internals documentation can be found in the Xen
source tree under docs/misc... here is the document:

http://lists.xensource.com/archives/html/xen-devel/2010-04/msg01031.html 

There is a brief discussion about page deduplication and
the data structures used to support it... other than
that and the code, there are no other details but
I would be happy to respond to specific questions.

There are also some performance results from the
last Xen Summit North America here:

http://oss.oracle.com/projects/tmem/dist/documentation/presentations/TranscendentMemoryXenSummit2010.pdf 

Note that the deduplication is performed only on pages
in tmem ephemeral pools.  If you are interested in page
sharing across all guest memory, that is a completely different
project.

Thanks,
Dan

> -----Original Message-----
> From: Kaustubh Kabra [mailto:kaustubhwise@gmail.com]
> Sent: Thursday, August 26, 2010 6:01 AM
> To: Xen-devel@lists.xensource.com
> Subject: [Xen-devel] Memory de-duplication
> 
> I have gone through the details of tmem and the patch provided by
> a group consisting Dan Magenheimer  as,
> 
> [Xen-devel] [PATCH] [xen-unstable] tmem: add page deduplication with
> opt .
> http://lists.xensource.com/archives/html/xen-devel/2010-
> 04/msg00148.html
> 
> The further details of the project as such are not available . So I
> request someone,who is aware of further development, to provide
> information about current status of the project.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Memory de-duplication

[Kaustubh Kabra]

[-- Attachment #1.1: Type: text/plain, Size: 3789 bytes --]

     Our idea of implementation suggests to bring the memory manager from
the kernel of the Dom U s to the hypervisor level and directly map the *memory
management related system calls to  the hypercalls*. Then allocate pages in
the main memory after performing de-duplication and return the address. So,
the aim is to have a *single memory manager* running at hypervisor level.

     When the RAM becomes full a *shared swap* area will be used further
reducing the need for an explicit swap within each DomU hence saving
significant amount of disk space. Will such an implementation be useful?
What are the expected challenges?

We were thinking of implementing such a idea as our final year project.

Regards,
Kaustubh Kabra
Aditya Gadre
Ashwin Vasani
Keshav Darak

On Fri, Aug 27, 2010 at 10:43 PM, Kaustubh Kabra <kaustubhwise@gmail.com>wrote:

> Hi Dan,
>
> Yes, I have been thinking of implementing common-page sharing for
> multiple guest OSes for Xen. This will be similar to the way KVM
> benefits because of the KSM feature in the Linux kernel.
>
> I found your patch for sharing ephemeral pages in the same tmem pool while
> searching further on the same topic. As I understand it the ephemeral
> pages
> are the pages that are read-only, i.e. txt section of executables etc. Is
> this
> understanding correct?
>
> Now that this is in place, I was thinking about extending this further
> to all the pages in the Guest OS's memory and use COW for read-write
> pages. I have started reading up the tmem architecture document and
> also your patch to have a better understanding of the system. Once I
> have digested this, I'll come up with a proposal towards the same.
>
> Do you have any thoughts on the concept / anticipated roadblocks ?
>
>
> On Thu, Aug 26, 2010 at 7:49 PM, Dan Magenheimer <
> dan.magenheimer@oracle.com> wrote:
>
>> Hello Kaustubh --
>>
>> I'm sorry I didn't reply to your earlier direct email.
>>
>> Tmem internals documentation can be found in the Xen
>> source tree under docs/misc... here is the document:
>>
>> http://lists.xensource.com/archives/html/xen-devel/2010-04/msg01031.html
>>
>> There is a brief discussion about page deduplication and
>> the data structures used to support it... other than
>> that and the code, there are no other details but
>> I would be happy to respond to specific questions.
>>
>> There are also some performance results from the
>> last Xen Summit North America here:
>>
>>
>> http://oss.oracle.com/projects/tmem/dist/documentation/presentations/TranscendentMemoryXenSummit2010.pdf
>>
>> Note that the deduplication is performed only on pages
>> in tmem ephemeral pools.  If you are interested in page
>> sharing across all guest memory, that is a completely different
>> project.
>>
>> Thanks,
>> Dan
>>
>> > -----Original Message-----
>> > From: Kaustubh Kabra [mailto:kaustubhwise@gmail.com]
>> > Sent: Thursday, August 26, 2010 6:01 AM
>> > To: Xen-devel@lists.xensource.com
>> > Subject: [Xen-devel] Memory de-duplication
>> >
>> > I have gone through the details of tmem and the patch provided by
>> > a group consisting Dan Magenheimer  as,
>> >
>> > [Xen-devel] [PATCH] [xen-unstable] tmem: add page deduplication with
>> > opt .
>> > http://lists.xensource.com/archives/html/xen-devel/2010-
>> > 04/msg00148.html
>> >
>> > The further details of the project as such are not available . So I
>> > request someone,who is aware of further development, to provide
>> > information about current status of the project.
>> >
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xensource.com
>> > http://lists.xensource.com/xen-devel
>>
>
>
>
> --
> *Kaustubh Kabra
> http://www.kaustubhwise.000a.biz*
>
>
>


-- 
*Kaustubh Kabra
http://www.kaustubhwise.000a.biz*

[-- Attachment #1.2: Type: text/html, Size: 5697 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

RE: Memory de-duplication

[Dan Magenheimer]

[-- Attachment #1.1: Type: text/plain, Size: 4662 bytes --]

The biggest challenge will be that the hypervisor does not contain any device drivers.  This will cause two major problems:

 

1)      When a userland application does a "read", currently the kernel is responsible for fetching the data from the disk.  Xen can't do that without device drivers.  The same is true for "write".

2)      A shared swap area requires disk drivers so the hypervisor can't swap.

 

You could build your sharing code in dom0 but that is very similar to Satori.

 

From: Kaustubh Kabra [mailto:kaustubhwise@gmail.com] 
Sent: Sunday, August 29, 2010 10:54 PM
To: Xen-devel@lists.xensource.com
Cc: Dan Magenheimer; Konrad Wilk
Subject: Re: [Xen-devel] Memory de-duplication

 

     Our idea of implementation suggests to bring the memory manager from the kernel of the Dom U s to the hypervisor level and directly map the memory management related system calls to  the hypercalls. Then allocate pages in the main memory after performing de-duplication and return the address. So, the aim is to have a single memory manager running at hypervisor level. 

     When the RAM becomes full a shared swap area will be used further reducing the need for an explicit swap within each DomU hence saving significant amount of disk space. Will such an implementation be useful? What are the expected challenges? 

We were thinking of implementing such a idea as our final year project.

Regards,
Kaustubh Kabra
Aditya Gadre
Ashwin Vasani
Keshav Darak

On Fri, Aug 27, 2010 at 10:43 PM, Kaustubh Kabra <HYPERLINK "mailto:kaustubhwise@gmail.com"kaustubhwise@gmail.com> wrote:

Hi Dan,

Yes, I have been thinking of implementing common-page sharing for
multiple guest OSes for Xen. This will be similar to the way KVM
benefits because of the KSM feature in the Linux kernel.

I found your patch for sharing ephemeral pages in the same tmem pool while
searching further on the same topic. As I understand it the ephemeral pages 
are the pages that are read-only, i.e. txt section of executables etc. Is this
understanding correct?

Now that this is in place, I was thinking about extending this further
to all the pages in the Guest OS's memory and use COW for read-write
pages. I have started reading up the tmem architecture document and
also your patch to have a better understanding of the system. Once I
have digested this, I'll come up with a proposal towards the same.

Do you have any thoughts on the concept / anticipated roadblocks ?

 

On Thu, Aug 26, 2010 at 7:49 PM, Dan Magenheimer <HYPERLINK "mailto:dan.magenheimer@oracle.com" \ndan.magenheimer@oracle.com> wrote:

Hello Kaustubh --

I'm sorry I didn't reply to your earlier direct email.

Tmem internals documentation can be found in the Xen
source tree under docs/misc... here is the document:

http://lists.xensource.com/archives/html/xen-devel/2010-04/msg01031.html

There is a brief discussion about page deduplication and
the data structures used to support it... other than
that and the code, there are no other details but
I would be happy to respond to specific questions.

There are also some performance results from the
last Xen Summit North America here:

http://oss.oracle.com/projects/tmem/dist/documentation/presentations/TranscendentMemoryXenSummit2010.pdf

Note that the deduplication is performed only on pages
in tmem ephemeral pools.  If you are interested in page
sharing across all guest memory, that is a completely different
project.

Thanks,
Dan


> -----Original Message-----
> From: Kaustubh Kabra [mailto:HYPERLINK "mailto:kaustubhwise@gmail.com" \nkaustubhwise@gmail.com]
> Sent: Thursday, August 26, 2010 6:01 AM
> To: HYPERLINK "mailto:Xen-devel@lists.xensource.com" \nXen-devel@lists.xensource.com
> Subject: [Xen-devel] Memory de-duplication
>
> I have gone through the details of tmem and the patch provided by
> a group consisting Dan Magenheimer  as,
>
> [Xen-devel] [PATCH] [xen-unstable] tmem: add page deduplication with
> opt .
> http://lists.xensource.com/archives/html/xen-devel/2010-
> 04/msg00148.html
>
> The further details of the project as such are not available . So I
> request someone,who is aware of further development, to provide
> information about current status of the project.
>

> _______________________________________________
> Xen-devel mailing list
> HYPERLINK "mailto:Xen-devel@lists.xensource.com" \nXen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel





-- 

Kaustubh Kabra
http://www.kaustubhwise.000a.biz






-- 
Kaustubh Kabra
http://www.kaustubhwise.000a.biz



[-- Attachment #1.2: Type: text/html, Size: 13588 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel