public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Izik Eidus <izike@qumranet.com>
To: Avi Kivity <avi@qumranet.com>
Cc: weigelt@metux.de,
	linux kernel list <linux-kernel@vger.kernel.org>,
	kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: Automatic page sharing/consolidation
Date: Wed, 16 Apr 2008 15:51:22 +0300	[thread overview]
Message-ID: <4805F64A.5070800@qumranet.com> (raw)
In-Reply-To: <4805E5E9.4080402@qumranet.com>

Avi Kivity wrote:
> Enrico Weigelt wrote:
>> Hi folks,
>>
>> I'm using dozens of VE's / jails to separate applications
>> (even complete webapps w/ their own httpd) for easier maintenance
>> and better security. But this tends to consume a lot of memory,
>> since code sharing (.so's) cannot take effect here (each jail/VE
>> has it's completely own tree).
>> Now I wonder if it might be possible to let the kernel automatically
>> find out equal pages and map them together.
>> A little compasion showed up that at least 50% of the code could be
>> shared (maybe more with some tuning, and maybe even data). So it's
>> (IMHO) really worth it.
>>
>> Would this be possible ? What had to be done for this ?
>>   
> 
> Izik (copied) is working on this for kvm.  Results so far are very
> encouraging, but currently merged pages are not swappable.
> 
we have module that posted with kernel patchs in the mm list, you can actualy run it and play with it
there were some bugs that we fixed with it, but i am still not sending it, beacuse i change there quite alot of things
in order to get swapping possible for the pages that are shared.
-- 
woof.

      reply	other threads:[~2008-04-16 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16  1:30 Automatic page sharing/consolidation Enrico Weigelt
2008-04-16 11:41 ` Avi Kivity
2008-04-16 12:51   ` Izik Eidus [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=4805F64A.5070800@qumranet.com \
    --to=izike@qumranet.com \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=weigelt@metux.de \
    /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