Date: Thu, 9 May 1996 15:58:50 -0700 From: asami@cs.berkeley.edu (Satoshi Asami) To: current@freebsd.org Cc: nisha@cs.berkeley.edu Subject: Max data segment size Message-ID: <199605092258.PAA14319@sunrise.cs.berkeley.edu>
next in thread | raw e-mail | index | archive | help
These are in /sys/i386/include/vmparam.h: === /* * Virtual memory related constants, all in bytes */ #define MAXTSIZ (16UL*1024*1024) /* max text size */ #ifndef DFLDSIZ #define DFLDSIZ (64UL*1024*1024) /* initial data size limit */ #endif #ifndef MAXDSIZ #define MAXDSIZ (128UL*1024*1024) /* max data size */ #endif #ifndef DFLSSIZ #define DFLSSIZ (8UL*1024*1024) /* initial stack size limit */ #endif #ifndef MAXSSIZ #define MAXSSIZ (64UL*1024*1024) /* max stack size */ #endif #ifndef SGROWSIZ #define SGROWSIZ (128UL*1024) /* amount to grow stack */ #endif === 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605092258.PAA14319>