From owner-freebsd-stable Tue Dec 18 14:35:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id F1FA337B419 for ; Tue, 18 Dec 2001 14:35:41 -0800 (PST) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id PAA02557; Tue, 18 Dec 2001 15:35:39 -0700 (MST) (envelope-from chad) Date: Tue, 18 Dec 2001 15:35:39 -0700 From: "Chad R. Larson" To: Ross Lippert Cc: freebsd-stable@FreeBSD.ORG Subject: Re: What are the current memory limits on x86? Message-ID: <20011218153539.C1557@freeway.dcfinc.com> References: <200112182221.OAA28057@eskimo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112182221.OAA28057@eskimo.com>; from ripper@eskimo.com on Tue, Dec 18, 2001 at 02:21:56PM -0800 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 On Tue, Dec 18, 2001 at 02:21:56PM -0800, Ross Lippert wrote: > > 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. #include #include #include -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message