From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Hanquez Subject: Re: [PATCH 0 of 3] libxl: memory leaks Date: Tue, 3 Aug 2010 11:51:47 +0100 Message-ID: <4C57F4C3.9090205@eu.citrix.com> References: <1280754703.18490.65.camel@qabil.uk.xensource.com> <4C56C60D.5060702@eu.citrix.com> <1280757928.18490.72.camel@qabil.uk.xensource.com> <4C57CC53.7030107@eu.citrix.com> <1280830700.18490.82.camel@qabil.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1280830700.18490.82.camel@qabil.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Gianni Tedesco (3P)" Cc: Ian Campbell , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 03/08/10 11:18, Gianni Tedesco (3P) wrote: > I wasn't aware that was the original design. It's certainly not the case > right now. it has unfortunately diverged in some calls indeed. > AFAICS that scheme would only guarantee everything has been freed if the > caller calls ctx_free() at appropriate points. If libxl were used in a > daemon, for example, it would not be simple to come up with a scheme > that guarantees memory bounds that are independent from uptime. This scheme is already in place in the ocaml binding -- Vincent