From: Jacob Faber Kloster <jk@cs.aau.dk>
To: Kip Macy <kip.macy@gmail.com>
Cc: xen-devel@lists.xensource.com, d515a@cs.aau.dk
Subject: Re: CoW memory and Parallax questions.
Date: Tue, 04 Oct 2005 13:14:27 +0200 [thread overview]
Message-ID: <1128424468.5265.22.camel@localhost.localdomain> (raw)
In-Reply-To: <b1fa29170510031212x1609935etaa812e8d8481673d@mail.gmail.com>
On Mon, 2005-10-03 at 12:12 -0700, Kip Macy wrote:
> They aren't mutually exclusive, but a content-based approach, although
> more flexible, seems like it would inevitably be much heavier weight.
> What is your solution targeted towards?
>
> -Kip
Indeed a combination of the two could be in order to avoid some
unnecessary processing. Also there is no doubt that content based
sharing uses more processing time, but it is more generally applicable
than the 'forking' scheme. For instance it seems hard to come up with a
scheme that allows sharing of memory when migrating VMs. Furthermore as
VMs, in the forking scheme, have run for a longer period of time, we
expect the percent of sharing to decrease. Content based sharing will
allow us to identify sharing that was not possible at the time of
forking.
Our solution is thus meant as an option when starting several VMs that
are similar, but not identical from start. Perhaps the processing
overhead of doing content based sharing is too large, but we can't
really know for certain before we have done some experiments.
Best regards
Jacob Faber Kloster (group email d515a@cs.aau.dk)
prev parent reply other threads:[~2005-10-04 11:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 11:52 CoW memory and Parallax questions Prashanth Radhakrishnan
2005-10-01 18:58 ` Michael Vrable
2005-10-01 23:04 ` Andrew Warfield
2005-10-03 16:20 ` Jacob Faber Kloster
2005-10-03 19:12 ` Kip Macy
2005-10-04 8:53 ` Jacob Gorm Hansen
2005-10-04 11:45 ` Jacob Faber Kloster
2005-10-04 17:34 ` Kip Macy
2005-10-20 17:45 ` cannot get console access to newly created domain Xin Zhao
2005-10-20 17:57 ` Ewan Mellor
2005-10-20 18:10 ` zhaoxin
2005-10-20 18:31 ` Ewan Mellor
2005-10-04 11:14 ` Jacob Faber Kloster [this message]
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=1128424468.5265.22.camel@localhost.localdomain \
--to=jk@cs.aau.dk \
--cc=d515a@cs.aau.dk \
--cc=kip.macy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.