From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lakshitha Harshan Subject: Memory Sharing Date: Tue, 26 Jul 2011 13:03:48 +0530 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1906498301==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel List-Id: xen-devel@lists.xenproject.org --===============1906498301== Content-Type: multipart/alternative; boundary=0003255581c2d4f3e604a8f3f32a --0003255581c2d4f3e604a8f3f32a Content-Type: text/plain; charset=ISO-8859-1 Hi, I'm doing a research project related to memory sharing. In my project I'm trying to share the memory pages in kernel code segments. These kernels are identical. I have carried out some experiments to analyze these memory pages. Results concluded that no modifications occurs on these memory pages at runtime. But after sharing these pages using nominate and share functions, 5 memory pages calls unshare() operation just after sharing the code pages. So my question is, if no modifications occurs at runtime, how could be possible to call "unshare()"? Thanks, Harshan --0003255581c2d4f3e604a8f3f32a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I'm doing a research project related to memory s= haring. In my project I'm trying to share the memory pages in kernel co= de segments. These kernels are identical.=A0
I have carried out s= ome experiments to analyze these memory pages. Results concluded that no mo= difications occurs on these memory pages at runtime.

But after sharing these pages using nominate and share = functions, 5 memory pages calls unshare() operation just after sharing the = code pages.

So my question is, if no modifications= occurs at runtime, how could be possible to call "unshare()"?

Thanks,

Harshan
--0003255581c2d4f3e604a8f3f32a-- --===============1906498301== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1906498301==--