From: Lakshitha Harshan <harshan.dll@gmail.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Memory Sharing
Date: Tue, 26 Jul 2011 13:03:48 +0530 [thread overview]
Message-ID: <CAH-yA4TdWn6dFf=CSpXe16r5PW+otbqBph6_um_NWHGv4_LLDw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 577 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 731 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2011-07-26 7:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 7:33 Lakshitha Harshan [this message]
2011-07-26 9:51 ` Memory Sharing Tim Deegan
-- strict thread matches above, loose matches on Subject: below --
2016-04-18 16:19 memory sharing sepanta s
2016-02-04 21:04 Memory Sharing hanji unit
2016-02-05 0:29 ` Tamas K Lengyel
2016-02-05 10:40 ` David Vrabel
2011-06-16 14:15 Lakshitha Harshan
2011-06-19 23:34 ` Jui-Hao Chiang
2011-06-14 5:04 Lakshitha Harshan
2011-06-14 8:10 ` Tim Deegan
2011-06-01 3:45 Lakshitha Harshan
2011-06-01 9:46 ` Tim Deegan
2011-05-24 7:17 Lakshitha Harshan
2011-05-24 9:19 ` Tim Deegan
2011-05-03 4:49 Lakshitha Harshan
2011-05-03 12:05 ` Tim Deegan
2011-04-26 9:52 Lakshitha Harshan
2011-04-09 6:37 Lakshitha Harshan
2011-04-09 8:36 ` Keir Fraser
2011-04-03 8:28 Memory sharing Lakshitha Harshan
2011-04-03 8:58 ` Keir Fraser
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='CAH-yA4TdWn6dFf=CSpXe16r5PW+otbqBph6_um_NWHGv4_LLDw@mail.gmail.com' \
--to=harshan.dll@gmail.com \
--cc=xen-devel@lists.xensource.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).