Messages in this thread | | | Date | Mon, 6 Feb 2006 15:56:34 +0100 (MET) | From | Jan Engelhardt <> | Subject | Re: [PATCH ] VMSPLIT config options (with default config fixed) |
| |
>> >> 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/
| |