From owner-freebsd-current  Thu May  9 18:56:34 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA01422
          for current-outgoing; Thu, 9 May 1996 18:56:34 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA01413
          for <current@freebsd.org>; Thu, 9 May 1996 18:56:29 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id UAA00255; Thu, 9 May 1996 20:55:01 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199605100155.UAA00255@dyson.iquest.net>
Subject: Re: Max data segment size
To: asami@cs.berkeley.edu (Satoshi Asami)
Date: Thu, 9 May 1996 20:55:01 -0500 (EST)
Cc: current@freebsd.org, nisha@cs.berkeley.edu
In-Reply-To: <199605092258.PAA14319@sunrise.cs.berkeley.edu> from "Satoshi Asami" at May 9, 96 03:58:50 pm
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> I tried doing an OPTIONS "MAXDSIZ=268435456" in my kernel config file,
> and the resulting kernel seems to be doing ok, and at least it passes
> the "malloc 1MB chunks until you blow up" test with flying colors (I
> know, it's not much of a test, I'm now running fsck with a 140-MB
> data segment which instigated this).
> 
> What are the rationales behind this being in a machine-specific system
> header file, in other words, does this mean that I can't increase the
> max data segment size beyond 128MB on an x86?  Did I just stomp on
> someone's toe in my quest to the biggest filesystem in the world?
> 
> Satoshi
> 
> 
I think that you should have no problem unless you don't leave enough
space for shared libs and/or stack...

John