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] [PATCH 0/2] Change xs_read_watch interfaces to support v

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH 0/2] Change xs_read_watch interfaces to support variable arguments
From: Ewan Mellor <Ewan.Mellor@xxxxxxxxxxxx>
Date: Tue, 4 Oct 2005 07:55:36 +0100
Delivery-date: Tue, 04 Oct 2005 09:47:31 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4342087F.5010505@xxxxxxxxxx>
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: <4342087F.5010505@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Oct 03, 2005 at 11:43:43PM -0500, Anthony Liguori wrote:

> The following set of changes modify the read_watch interface in 
> userspace and in the kernel to support variable arguments.  This is in 
> preparation for adding domid to @{introduce,release}Domain watches.  
> This will allow backends to automatically reap on domain destruction 
> which should eliminate a large number of the zombie problems we're 
> having on domain destruction since Xend no longer plays a role in 
> freeing that memory.

Hi Anthony,

What you've done in your patch stands as a sensible thing on its own, I think,
so I'm not objecting to that, but I am interested in why you think it will
help with the zombies.  On domain destruction, xend is _supposed_ to remove
all the relevant entries of the store, and the backend drivers are _supposed_
to notice this and close themselves down.  If you have evidence that either of
those things aren't happening, then we should regard that as a bug,
independent of your patch.  Have you seen that happening?

Ewan.

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