Increase memory limits for IcedTea
Andrew Haley
aph at redhat.com
Thu Oct 11 02:28:10 PDT 2007
Florian Weimer writes:
> * Andrew Haley:
>
> > 3. There may be other untoward consequences of removing these limits:
>
> It tends to break with "vm.overcommit_memory = 2". AFAICT, IcedTea uses
> the wrong flags with mmap/mprotect, or there is a kernel bug.
>
> Unfortunately, it's not documented which flags you need to pass to make
> an allocation not count against the beancounter. Currently,
> MAP_NORESERVE does not work, but allocating with PROT_NONE and setting
> the proper flags later does.
>
> It would be great if you could resolve this with the kernel team. (It's
> not just Java which would benefit from clear documentation, many other
> memory managers would.)
I'm sorry, but you're just being a bit too obscure for me. What do
you mean by "it tends to break"?
If you could give an example to test, with a description of what you
think should happen and what does happen, then I could talk to the
kernel team.
Andrew.
--
Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, UK
Registered in England and Wales No. 3798903
More information about the distro-pkg-dev
mailing list