From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: "Gianni Tedesco (3P)" <gianni.tedesco@citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0 of 3] libxl: memory leaks
Date: Tue, 3 Aug 2010 11:51:47 +0100 [thread overview]
Message-ID: <4C57F4C3.9090205@eu.citrix.com> (raw)
In-Reply-To: <1280830700.18490.82.camel@qabil.uk.xensource.com>
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
next prev parent reply other threads:[~2010-08-03 10:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 12:31 [PATCH 0 of 3] libxl: memory leaks Ian Campbell
2010-08-02 12:31 ` [PATCH 1 of 3] libxc: free thread specific hypercall buffer on xc_interface_close Ian Campbell
2010-08-02 12:31 ` [PATCH 2 of 3] libxl: fix memory leak in libxl_name_to_domid Ian Campbell
2010-08-02 12:31 ` [PATCH 3 of 3] xl: fix memory leaks in xl create Ian Campbell
2010-08-02 13:11 ` [PATCH 0 of 3] libxl: memory leaks Gianni Tedesco
2010-08-02 13:20 ` Vincent Hanquez
2010-08-02 14:05 ` Gianni Tedesco
2010-08-03 7:59 ` Vincent Hanquez
2010-08-03 10:18 ` Gianni Tedesco
2010-08-03 10:51 ` Vincent Hanquez [this message]
2010-08-03 12:16 ` Gianni Tedesco
2010-08-03 13:37 ` Vincent Hanquez
2010-08-03 14:02 ` Gianni Tedesco
2010-08-03 14:51 ` Ian Campbell
2010-08-03 17:07 ` Stefano Stabellini
2010-08-03 17:11 ` Stefano Stabellini
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=4C57F4C3.9090205@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=gianni.tedesco@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).