On Wed, 14 Sep 2005, Juho Snellman wrote:
> The dynamic space limits are set at compile-time. To increase the
> allocation, edit the definition of DYNAMIC-SPACE-END in
> src/compiler/x86-64/parms.lisp and recompile SBCL. I'd rather not make
> the space any larger than 8GB in the default distribution until some
> other issues are solved, since the GENCGC page tables use too much
> memory with large spaces.
I was just to send a very similar question to the list. Unlike the orignal
poster, I was not runing out of memory at "runtime", but when dumping an image
with save-lisp-and-die, I was running out of static space, since I had
a really big hashtable. I can then follow your advice and recompile sbcl
with a modified parms.lisp, but my question is:
- What is safe to modify. Obvouosly, the memory areas cannot overlap, but which
restrictions are on these memory areas anyway.
- Why are these memory areas at fixed location? My guess would be that it has
something with typetags to do, or that it is needed by gc-algorithm. Just
I also use linux on AMD64.
Gisle Sælensminde, Phd student, Scientific programmer
Computational biology unit, University of Bergen, Norway