From e113e5011c85c82cc473104d211d7d0765840c15 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Fri, 15 Mar 2013 14:46:44 +0100 Subject: update faq --- hurd/running/debian/faq/ram_limit.mdwn | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 hurd/running/debian/faq/ram_limit.mdwn (limited to 'hurd/running/debian/faq/ram_limit.mdwn') diff --git a/hurd/running/debian/faq/ram_limit.mdwn b/hurd/running/debian/faq/ram_limit.mdwn new file mode 100644 index 00000000..ac5cefe7 --- /dev/null +++ b/hurd/running/debian/faq/ram_limit.mdwn @@ -0,0 +1,21 @@ +[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled +[[GNU Free Documentation License|/fdl]]."]]"""]] + +[[!meta title="830 MiB RAM Limit"]] + +Just like any 32bit OS without bad tricks, GNU Mach does 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. + +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 +it can see via GRUB's `upppermem` feature. Add `uppermem 786432` to GRUB's Hurd +entry in `menu.lst`. -- cgit v1.2.3