All of lore.kernel.org
 help / color / mirror / Atom feed
From: urmk@reason.marist.edu
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: Xen-devel@lists.sourceforge.net
Subject: Re: Copy-on-write memory to allow many more xenU domains per machine
Date: Tue, 2 Nov 2004 16:50:54 -0500	[thread overview]
Message-ID: <20041102215054.GA30274@reason.marist.edu> (raw)
In-Reply-To: <E1CP6Gz-0008CU-00@mta1.cl.cam.ac.uk>

Check the s/390 port of the kernel for the XIP2 filesystem.  It exploits
the z/VM shared memory system to make a read-only ext2 like filesystem
that is shared amonst all the guests - and uses execute-in-place.  Any
binaries on the xip2 filesystem aren't cached into local shared memory,
they're just mapped across.

This lets an admin build explicit shared systems, does shared ro-memory
nicely, etc.  Might be worth looking into implementing similar in Xen.

Apologies if this was already discussed/noticed,

-m

On Tue, Nov 02, 2004 at 09:33:00PM +0000, Ian Pratt wrote:
>  
> > What about having a special variant of the pte-update operation, which 
> > takes as input a pointer to a pte-entry, and will change that entry into 
> > a read-only mapping of the same page contents, though perhaps with a 
> > different frame number in the pte.
> 
> I'm still not convinced we wouldn't get most of the benefit by
> just sharing pages read from the block/file system, and hence
> avoiding all the hashing. 
> 
> Collecting this data is actually very easy -- its just a case of
> coming up with a few "realistic usage scenarios" in which to
> collect the data. We'd be happy to work with someone to do
> this...
> 
> Ian
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

      reply	other threads:[~2004-11-02 21:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08  8:59 Shadow page tables? Chengyuan Li
2004-10-08  9:11 ` Keir Fraser
2004-10-10  2:52   ` Chengyuan Li
2004-10-12 18:50   ` Michael Vrable
2004-10-12 20:09     ` Andrew Warfield
2004-10-13  1:53       ` Michael Vrable
2004-10-21  8:38     ` Peri Hankey
2004-10-25 12:12     ` Copy-on-write memory to allow many more xenU domains per machine Peri Hankey
2004-10-25 12:21       ` Ian Pratt
2004-10-25 18:24         ` David Hopwood
2004-10-25 19:52           ` Ronald G. Minnich
2004-10-25 20:19           ` Ian Pratt
2004-10-25 22:38       ` Michael Vrable
2004-10-26  8:15         ` Peri Hankey
2004-10-26 18:30           ` Michael Vrable
2004-10-26 19:43             ` Ian Pratt
2004-10-26 22:19               ` Michael Vrable
2004-11-02 20:55         ` Jacob Gorm Hansen
2004-11-02 21:33           ` Ian Pratt
2004-11-02 21:50             ` urmk [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=20041102215054.GA30274@reason.marist.edu \
    --to=urmk@reason.marist.edu \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=Xen-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 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.