WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Memory overcommit

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Memory overcommit
From: Jacob Gorm Hansen <jacobg@xxxxxxx>
Date: Tue, 13 Dec 2005 17:25:19 +0100
Cc: xen-devel List <xen-devel@xxxxxxxxxxxxxxxxxxx>, treed@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 13 Dec 2005 16:27:03 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nRO5cRwVJOI/AFub2z4UyUHZFKHiSoMBDHKrokb9zvJNXj918x5XMsMz1G4FkPVM3Gww8Lu18M91BZlpLmNUEDXOhMJLbnUv7TZV2eElrucSm7dvramBD+IjXzbCwBokKIYm/xYaxBqygi3LgTiO5NW3+T9hQGIY2TvG4qrH2ao=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <2e9671df40bbaec57e383069204b80d8@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4399FE6A.9030000@xxxxxxxxxxxxxxxxxxxxx> <b1fa29170512101800i632ce67ft8a7139d4f1305598@xxxxxxxxxxxxxx> <56856b9e32e3424c70c93db018f41d49@xxxxxxxxxxxx> <Pine.LNX.4.63.0512111458120.26350@xxxxxxxxxxxxxxxxxxxxxx> <2e9671df40bbaec57e383069204b80d8@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 12/13/05, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
>
> On 11 Dec 2005, at 19:59, Rik van Riel wrote:
>
> >> Even better, if each domain is only used occasionally, then you could
> >> save them to disc and restore them on demand.
> >
> > How would one implement such a "wake on LAN" functionality
> > for Xen domains ?
>
> There are various ways. Maybe require explicit signalling from the user
> via some command to the control-plane tools (start up my domain / shut
> down my domain). You could also do it implicitly (although it may
> require some iptables hacking) by tracking network connections to the
> domain's IP address -- start it up on first connection / shut it down
> when last connection finishes.

Or you could use my self-checkpointing code to have the domain save
itself, then free most of its pages, except for a small stub that
would listen for some 'wake up' event on the network interface (e.g. a
TCP SYN packet). The stub could then allocate new pages and resume the
checkpoint from disk.

Jacob

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>