Ian Campbell writes ("Re: [Xen-devel] Current LibXL Status"):
> The only one I can find which isn't one of this is
> in libxl__event_disaster, and that is only if the applications (or language
> bindings) haven't provided a suitable disaster callback.
libxl__event_dis
On Thu, 2016-02-18 at 17:39 +, Ian Campbell wrote:
> On Thu, 2016-02-18 at 17:26 +, George Dunlap wrote:
>
> > According to them, the ocaml garbage collector never frees memory. It
> > grows its own internal heap as necessary, but it never reduces the
> > size of its heap.
>
> Assume tha
On Thu, Feb 18, 2016 at 5:39 PM, Ian Campbell wrote:
> On Thu, 2016-02-18 at 17:26 +, George Dunlap wrote:
>
>> According to them, the ocaml garbage collector never frees memory. It
>> grows its own internal heap as necessary, but it never reduces the
>> size of its heap.
>
> Assume that's tr
On Thu, Feb 18, 2016 at 5:26 PM, Ian Campbell wrote:
> On Thu, 2016-02-18 at 17:19 +, Ian Jackson wrote:
>> George Dunlap writes ("Re: [Xen-devel] Current LibXL Status"):
>> > So what was the conclusion here? It looks like we've confirmed that
>> >
On Thu, 2016-02-18 at 17:26 +, George Dunlap wrote:
> According to them, the ocaml garbage collector never frees memory. It
> grows its own internal heap as necessary, but it never reduces the
> size of its heap.
Assume that's true: Wow!
Although, I presume this is a factor of the current/p
On Thu, 2016-02-18 at 17:19 +, Ian Jackson wrote:
> George Dunlap writes ("Re: [Xen-devel] Current LibXL Status"):
> > So what was the conclusion here? It looks like we've confirmed that
> > exit() is only called:
> >
> > 1. In the case of a mallo
On Thu, Nov 19, 2015 at 11:23 AM, Ian Campbell wrote:
> create !
> title it libxl exit() on ENOMEM incompatible with gc'd languages
> thanks
>
> On Thu, 2015-11-19 at 10:55 +, Andrew Cooper wrote:
>> On 19/11/15 09:20, Ian Campbell wrote:
>> > On Wed, 2015-11-18 at 18:32 +, Martin Osterloh
On Thu, 2016-02-18 at 17:09 +, George Dunlap wrote:
> On Thu, Nov 19, 2015 at 12:16 PM, Ian Campbell
> wrote:
> > On Thu, 2015-11-19 at 11:55 +, Ian Campbell wrote:
> > > On Thu, 2015-11-19 at 11:48 +, Ian Campbell wrote:
> > > > On Thu, 2015-11-19 at 11:33 +, Andrew Cooper wrote:
George Dunlap writes ("Re: [Xen-devel] Current LibXL Status"):
> So what was the conclusion here? It looks like we've confirmed that
> exit() is only called:
>
> 1. In the case of a malloc() failure
> 2. in libxl-save-helper (a separate process
On Thu, Nov 19, 2015 at 12:16 PM, Ian Campbell wrote:
> On Thu, 2015-11-19 at 11:55 +, Ian Campbell wrote:
>> On Thu, 2015-11-19 at 11:48 +, Ian Campbell wrote:
>> > On Thu, 2015-11-19 at 11:33 +, Andrew Cooper wrote:
>> > >
>> > > The majority of those are cases are not appropriate us
On 2015年11月19日 20:16, Ian Campbell wrote:
On Thu, 2015-11-19 at 11:55 +, Ian Campbell wrote:
On Thu, 2015-11-19 at 11:48 +, Ian Campbell wrote:
On Thu, 2015-11-19 at 11:33 +, Andrew Cooper wrote:
The majority of those are cases are not appropriate uses of exit().
AFAIIR, the *only
On Thu, Nov 19, 2015 at 11:23 AM, Ian Campbell wrote:
> create !
> title it libxl exit() on ENOMEM incompatible with gc'd languages
> thanks
Actually, can I suggest that someone send a new thread with an
appropriate title, so that people who aren't directly following the
thread know what kinds of
On Thu, 2015-11-19 at 11:55 +, Ian Campbell wrote:
> On Thu, 2015-11-19 at 11:48 +, Ian Campbell wrote:
> > On Thu, 2015-11-19 at 11:33 +, Andrew Cooper wrote:
> > >
> > > The majority of those are cases are not appropriate uses of exit().
> > > AFAIIR, the *only* valid use of exit()
On Thu, 2015-11-19 at 11:48 +, Ian Campbell wrote:
> On Thu, 2015-11-19 at 11:33 +, Andrew Cooper wrote:
> >
> > The majority of those are cases are not appropriate uses of exit().
> > AFAIIR, the *only* valid use of exit() in a library is to clean up in a
> > child process from a librar
On Thu, 2015-11-19 at 11:33 +, Andrew Cooper wrote:
>
> The majority of those are cases are not appropriate uses of exit().
> AFAIIR, the *only* valid use of exit() in a library is to clean up in a
> child process from a library-initiated fork().
... or (in this case) in the libxl-save-helpe
On 19/11/15 11:23, Ian Campbell wrote:
> create !
> title it libxl exit() on ENOMEM incompatible with gc'd languages
> thanks
Can this be extended to "should not use exit() in general" ?
andrewcoop@andrewcoop:/local/xen.git/xen$ git grep exit\( --
:/tools/libxl/libxl*
../tools/libxl/libxl.c:1707:
create !
title it libxl exit() on ENOMEM incompatible with gc'd languages
thanks
On Thu, 2015-11-19 at 10:55 +, Andrew Cooper wrote:
> On 19/11/15 09:20, Ian Campbell wrote:
> > On Wed, 2015-11-18 at 18:32 +, Martin Osterloh wrote:
> >
> > > I wanted to inquire about the current state of
On 19/11/15 09:20, Ian Campbell wrote:
> On Wed, 2015-11-18 at 18:32 +, 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
On Thu, Nov 19, 2015 at 9:20 AM, Ian Campbell wrote:
> On Wed, 2015-11-18 at 18:32 +, 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 libvirt
On Wed, 2015-11-18 at 18:32 +, 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 e
Hello All,
I am currently working on the OpenXT project [1]. My work is currently
focused on creating a shim layer between XenMgr [2] (written in Haskell)
and LibXL. Goal is to replace the current XenOps/XenVM [3] (written in
OCaml).
I wanted to inquire about the current state of LibXL and in
21 matches
Mail list logo
