Re: [MirageOS-devel] Memory exhaustion in Mirage

[Masoud Koleini <masoud.koleini@xxxxxxxxxxxxxxxx>]

Yes, I have faced this problem several times when flooding the input 
port (similar error on the console). The allocated memory for the switch 
is 2GB, which is much higher than 64MB, but I guess bit rate should be 
higher too.
On 16/12/14 23:45, Anil Madhavapeddy wrote:
> On 16 Dec 2014, at 15:23, Masoud Koleini <masoud.koleini@xxxxxxxxxxxxxxxx> 
> wrote:
> > I am wondering if the following issue is already addressed:
> >
> > https://github.com/mirage/mirage-tcpip/issues/33
> >
> > https://lists.cam.ac.uk/pipermail/cl-mirage/2013-August/msg00104.html
> It probably still happens at 64MB of RAM -- it requires some code to adjust
> the GC parameters in the OCaml runtime to trigger a collection more often.
> It should be harmless however, since (as the bug report observes), a failure
> to allocate an Io_page results in a GC compaction that frees up memory so
> that the allocation eventually succeeds.
>
> Any particular reason for asking -- is the bug affecting your switch somehow?
>
> -anil




This message and any attachment are intended solely for the addressee and may 
contain confidential information. If you have received this message in error, 
please send it back to me, and immediately delete it.   Please do not use, copy 
or disclose the information contained in this message or in any attachment.  
Any views or opinions expressed by the author of this email do not necessarily 
reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment may 
still contain software viruses which could damage your computer system, you are 
advised to perform your own checks. Email communications with the University of 
Nottingham may be monitored as permitted by UK legislation.


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel