From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Current LibXL Status Date: Thu, 19 Nov 2015 10:55:09 +0000 Message-ID: <564DAA8D.5060305@citrix.com> References: <564CC43B.1000904@ainfosec.com> <1447924858.5647.15.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1447924858.5647.15.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell , Martin Osterloh , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 19/11/15 09:20, Ian Campbell wrote: > On Wed, 2015-11-18 at 18:32 +0000, Martin Osterloh wrote: > >> I wanted to inquire about the current state of LibXL and in particular >> if there are any issues with using it in long-running processes. > It is currently being used by libvirtd which I think has shaken out most of > the issues with that environment. > > There are certain to be other bugs, but nothing show-stopping. There really is a show-stopper, which I have stated before. Languages such as OCaml use -ENOMEM as a hint to run the garbage collector some more. I expect Haskell is the same. It is not appropriate for libxl (or any library for that matter) to use exit() as its method of resolving out-of-memory conditions. ~Andrew