> >>>>> "rif" == rif <[EMAIL PROTECTED]> writes: > > rif> I'm running CMUCL 19A debian release (from unstable) under a 2.6.7 > rif> kernel with highmem enabled. It's a laptop wit 2 GB of RAM. Without > rif> highmem, the OS only sees ~900 MB of RAM, but with it, it gets the > rif> full 2 GB. However, even with this patch enabled, when I start CMUCL > rif> with -dynamic-space-size 1280, (lisp::dynamic-space-size) returns > rif> 536870912. > > This seems odd. On my Suse 9 system, I can have a dynamic-space-size > of 800 MB (limited by available memory and swap on my machine). > dynamic-space-size returns the expected value. I don't think I have > highmem enabled. > > I've heard of people using 1.5 GB of heap on linux, so it's possible. > > Ray >
Oh, it's certainly possible on Linux in general. My desktop machine has 2 GB of RAM, and I can get over 1 GB in CMUCL no problem. The problem is specifically on my laptop. On the laptop only, I need to enable highmem to get at the full memory, and CMUCL seems to be unable to take advantage of this. Is this known, or is there any way to try and fix it? Anyone else have to use highmem to get at all their memory? In any case, I am certainly observing that starting CMU 19A with a dynamic space size of 1280 on a machine with 2 GB of RAM yields a much smaller dynamic space size, too small in which to work with my data. Any help or advice (especially if it's not "get a different computer") is appreciated. Cheers, rif
