On Mon, Feb 06, 2006 at 03:56:34PM +0100, Jan Engelhardt wrote:Not to mention that these (almost(*)) fail anyway when you have less than 2What userspace programs do depend on it?
there is a lot of userspace that assumes they can do 2Gb or even close
to 3Gb of memory allocations. Databases, java, basically anything with
threads. Sure for most of these its a configuration option to reduce
this, but that still doesn't mean it's a good idea to change from the
existing behavior...
GB of RAM.
it's not really overcommit... it can also be file mmaps or shared mmaps
of say tmpfs files (the later is common with oracle actually)
So, just as I did in the sample patch, the manual split shall depend on
EMBEDDED. Those who run fat databases with big malloc/mmap assumptions
don't probably belong to the group using CONFIG_EMBEDDED.
*sigh* well, the embeded folks are unlikely to have 1-3GB
why not use EXPERIMENTAL if you 'think' the option will
hurt the database folks who do not know to configure their
kernel ...