Date: Mon, 6 Feb 2006 15:56:34 +0100 (MET)
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Arjan van de Ven <arjan@infradead.org>
cc: Mark Lord <lkml@rtr.ca>, Ulrich Mueller <ulm@kph.uni-mainz.de>,
       Herbert Poetzl <herbert@13thfloor.at>, linux-kernel@vger.kernel.org,
       Jens Axboe <axboe@suse.de>, Linus Torvalds <torvalds@osdl.org>,
       Byron Stanoszek <gandalf@winds.org>, Ingo Molnar <mingo@elte.hu>,
       Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH ]  VMSPLIT config options (with default config fixed)
In-Reply-To: <1139174355.3131.50.camel@laptopd505.fenrus.org>
Message-ID: <Pine.LNX.4.61.0602061554550.31522@yvahk01.tjqt.qr>
References: <20060110132957.GA28666@elte.hu> <20060110133728.GB3389@suse.de>
  <Pine.LNX.4.63.0601100840400.9511@winds.org>  <20060110143931.GM3389@suse.de>
  <Pine.LNX.4.64.0601100804380.4939@g5.osdl.org> <43C3E9C2.1000309@rtr.ca> 
 <20060110173217.GU3389@suse.de> <43C3F0CA.10205@rtr.ca>  <43C403BA.1050106@pobox.com>
 <43C40803.2000106@rtr.ca>  <20060201222314.GA26081@MAIL.13thfloor.at> 
 <uhd7irpi7@a1i15.kph.uni-mainz.de>  <Pine.LNX.4.61.0602022144190.30391@yvahk01.tjqt.qr>
  <43E3DB99.9020604@rtr.ca>  <Pine.LNX.4.61.0602041204490.30014@yvahk01.tjqt.qr>
  <1139153913.3131.42.camel@laptopd505.fenrus.org> 
 <Pine.LNX.4.61.0602052212430.330@yvahk01.tjqt.qr> <1139174355.3131.50.camel@laptopd505.fenrus.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1083
Lines: 27

>> >> What 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...
>> > 
>> Not to mention that these (almost(*)) fail anyway when you have less than 2 
>> 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.


Jan Engelhardt
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/