From owner-freebsd-stable Tue Dec 18 14:22: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by hub.freebsd.org (Postfix) with ESMTP id 6E89737B405 for ; Tue, 18 Dec 2001 14:22:03 -0800 (PST) Received: from eskimo.com (ripper@eskimo.com [204.122.16.13]) by mx1.eskimo.com (8.9.1a/8.8.8) with ESMTP id OAA15169 for ; Tue, 18 Dec 2001 14:21:56 -0800 Received: (from ripper@localhost) by eskimo.com (8.9.1a/8.9.1) id OAA28057; Tue, 18 Dec 2001 14:21:56 -0800 (PST) Date: Tue, 18 Dec 2001 14:21:56 -0800 (PST) Message-Id: <200112182221.OAA28057@eskimo.com> From: Ross Lippert To: freebsd-stable@freebsd.org Subject: What are the current memory limits on x86? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I know someone having some trouble with a big memory machine running some other *nix, so I was curious about some stuff. (if the answers apply differently for the kernels of 4.4 and 5.0-CURRENT, please specify) Specifically, on an x86 with 4Gig of RAM, will the kernel let a single process access nearly all of it? I believe that on his current setup doing a >2Gig malloc returns NULL. In general, I am curious about what the current limits and gotcha's are for FreeBSD for large memory machines Intel and otherwise, but I am having a hard time finding something describing where the edge is. Thanks, -r To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message