linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Izik Eidus <izike@qumranet.com>,
	kvm-devel <kvm-devel@lists.sourceforge.net>,
	andrea@qumranet.com, dor.laor@qumranet.com, linux-mm@kvack.org,
	yaniv@qumranet.com
Subject: Re: [kvm-devel] [RFC][PATCH 0/5] Memory merging driver for Linux
Date: Thu, 24 Jan 2008 07:40:58 +0200	[thread overview]
Message-ID: <479824EA.7070603@qumranet.com> (raw)
In-Reply-To: <20080123231037.GA3629@sequoia.sous-sol.org>

Chris Wright wrote:
> * Izik Eidus (izike@qumranet.com) wrote:
>   
>> this module find this identical data (pages) and merge them into one 
>> single page
>> this new page is write protected so in any case the guest will try to 
>> write to it do_wp_page will duplicate the page
>>     
>
> What happens if you've merged more pages than you can recover on write
> faults?
>   

You start to swap.  Just like Linux when you start to write on fork()ed 
memory.

A management application may start taking measures, like inflating 
balloons and migrating to other hosts, but swapping is needed as a last 
resort measure.

-- 
Any sufficiently difficult bug is indistinguishable from a feature.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-01-24  5:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 16:05 Izik Eidus
2008-01-23 17:05 ` [kvm-devel] " Rik van Riel
2008-01-23 17:54   ` Andrea Arcangeli
2008-01-23 18:11     ` Izik Eidus
2008-01-24  5:38   ` Avi Kivity
2008-01-23 23:10 ` Chris Wright
2008-01-24  5:40   ` Avi Kivity [this message]
2008-01-24  9:26     ` Izik Eidus

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=479824EA.7070603@qumranet.com \
    --to=avi@qumranet.com \
    --cc=andrea@qumranet.com \
    --cc=chrisw@sous-sol.org \
    --cc=dor.laor@qumranet.com \
    --cc=izike@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-mm@kvack.org \
    --cc=yaniv@qumranet.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