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 1/2] reap the blktapctl thread and notify the tap

To: James Song <jsong@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 1/2] reap the blktapctl thread and notify the tapdisk backend driver to release resource like memory..
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Thu, 6 May 2010 16:57:50 +0100
Cc: Jim Fehlig <JFEHLIG@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, ian.jackson@xxxxxxxxxxxxx
Delivery-date: Thu, 06 May 2010 09:07:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BE16E900200002000085C21@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Newsgroups: chiark.mail.xen.devel
References: <4BE16E900200002000085C21@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
James Song writes ("[Xen-devel] [PATCH 1/2] reap the blktapctl thread and 
notify the tapdisk backend driver to release resource like memory.."):
> For this issue I had initial discussion thread before, more detail,
> please see :
> http://lists.xensource.com/archives/html/xen-devel/2010-04/msg01140.html.

This patch seems to remove the code which is responsible for reaping
qemu-dm on device model destruction.  I'm afraid I don't understand at
all how that could possibly be correct.  I admit xend is confusing and
it may be broken in this area but as far as I can tell this is a step
backwards.

Ian.

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

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