From: Jeff Dike <jdike@addtoit.com>
To: Jun OKAJIMA <okajima@digitalinfra.co.jp>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Sharing code pages between host and guest
Date: Tue, 14 Mar 2006 15:27:39 -0500 [thread overview]
Message-ID: <20060314202739.GC22286@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200603121426.AA00812@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
On Sun, Mar 12, 2006 at 11:26:09PM +0900, Jun OKAJIMA wrote:
> I am studying now for how you share same content page between host and guest.
> In other words, if host and guest use just very same binary of glibc,
> then, how to share code pages of glibc (or bash or...).
> I think one of the biggest problem of virtualization is memory,
> and one common technique to solve it is sharing pages, dont you?
That would certainly help, although you are giving up one advantage of
virtualization this way, which is the ability to have the guest and host
be running different versions of the kernel and/or userspace.
> My question is, if you share /lib through HostFS,
> can I share code pages of /lib/libc.6.so between host and guest?
If hostfs mmaps pages (which it currently doesn't, but is planned).
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-03-14 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 14:26 [uml-devel] Sharing code pages between host and guest Jun OKAJIMA
2006-03-14 20:27 ` Jeff Dike [this message]
2006-03-15 13:07 ` Jun OKAJIMA
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=20060314202739.GC22286@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=okajima@digitalinfra.co.jp \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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