From: Chris Wright <chrisw-69jw2NvuJkxg9hUCZPvPmw@public.gmane.org>
To: Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: andrea-atKUWr5tajBWk0Htik3J/w@public.gmane.org,
yaniv-atKUWr5tajBWk0Htik3J/w@public.gmane.org,
kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org
Subject: Re: [RFC][PATCH 0/5] Memory merging driver for Linux
Date: Wed, 23 Jan 2008 15:10:41 -0800 [thread overview]
Message-ID: <20080123231037.GA3629@sequoia.sous-sol.org> (raw)
In-Reply-To: <4794C2E1.8040607-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
* Izik Eidus (izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org) 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?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-01-23 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 16:05 [RFC][PATCH 0/5] Memory merging driver for Linux Izik Eidus
[not found] ` <4794C2E1.8040607-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-23 17:05 ` Rik van Riel
[not found] ` <20080123120510.4014e382-Fuq27k0DHcCSkoNiqTzCLQ@public.gmane.org>
2008-01-23 17:54 ` Andrea Arcangeli
[not found] ` <20080123175444.GH7141-lysg2Xt5kKMAvxtiuMwx3w@public.gmane.org>
2008-01-23 18:11 ` Izik Eidus
2008-01-24 5:38 ` Avi Kivity
2008-01-23 23:10 ` Chris Wright [this message]
[not found] ` <20080123231037.GA3629-JyIX8gxvWYPr2PDY2+4mTGD2FQJk+8+b@public.gmane.org>
2008-01-24 5:40 ` Avi Kivity
[not found] ` <479824EA.7070603-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
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=20080123231037.GA3629@sequoia.sous-sol.org \
--to=chrisw-69jw2nvujkxg9huczpvpmw@public.gmane.org \
--cc=andrea-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=yaniv-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
/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