summaryrefslogtreecommitdiff
path: root/faq/ram_limit.mdwn
diff options
context:
space:
mode:
authorJoshua Branson <jbranso@fastmail.com>2018-11-07 10:32:38 -0500
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2018-11-08 23:53:31 +0100
commit3e25a0fd194bbdb1838abb0a17832252eb03462a (patch)
tree42f11e17cf99aba0978047239fc15a4caa9c16a7 /faq/ram_limit.mdwn
parent1a8d5c728cc275f20d7f560e2760aa882c8ed502 (diff)
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.
Diffstat (limited to 'faq/ram_limit.mdwn')
-rw-r--r--faq/ram_limit.mdwn12
1 files changed, 8 insertions, 4 deletions
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