From 3e25a0fd194bbdb1838abb0a17832252eb03462a Mon Sep 17 00:00:00 2001 From: Joshua Branson Date: Wed, 7 Nov 2018 10:32:38 -0500 Subject: I am adding Richard's comment about mach's memory management issue to the open issues gnumach memory management page. I also added a link to the 64-bit port on the 830MB RAM limit page. --- faq/ram_limit.mdwn | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) (limited to 'faq/ram_limit.mdwn') diff --git a/faq/ram_limit.mdwn b/faq/ram_limit.mdwn index 5017925c..8e13f321 100644 --- a/faq/ram_limit.mdwn +++ b/faq/ram_limit.mdwn @@ -13,10 +13,14 @@ License|/fdl]]."]]"""]] [[!meta title="830 MiB RAM Limit"]] -Just like any 32-bit OS without bad tricks, GNU Mach can not cope well with lots -of memory. Latest versions of the Debian `gnumach` package will limit themselves -to around 1.7 GiB of memory. If you want more, you can twiddle the `VM_MAX_ADDRESS` -limit between kernelland and userland in `i386/include/mach/i386/vm_param.h`. +The 830MB RAM limit has been removed, but just like any 32-bit OS without bad tricks, +GNU Mach can not cope well with lots of memory. Latest versions of the Debian `gnumach` +package will limit themselves to 3 GiB of memory. If you want more, you can twiddle +the `VM_MAX_ADDRESS` limit between kernelland and userland in +`i386/include/mach/i386/vm_param.h`, but glibc and the hurd servers will not cope +well with less than 1 GB. + +There is a [[64-bit port|open_issues/64-bit_port]] in progress. If you have an older version, or still experience problems with `vmstat` (see above) reported much less memory than you have, the best is to limit the memory -- cgit v1.2.3