From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 26 Apr 2003 10:37:11 -0400 (EDT) From: Rik van Riel Subject: Re: TASK_UNMAPPED_BASE & stack location In-Reply-To: <459930000.1051302738@[10.10.2.4]> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: "Martin J. Bligh" Cc: linux-kernel , linux-mm mailing list , Andrew Morton List-ID: On Fri, 25 Apr 2003, Martin J. Bligh wrote: > Is there any good reason we can't remove TASK_UNMAPPED_BASE, and just shove > libraries directly above the program text? Red Hat seems to have patches to > dynamically tune it on a per-processes basis anyway ... What could be done is leave the stack where it is, but have malloc() space and mmap() space grow towards each other: 0 3G | |prog | malloc --> <-- mmap | stack | The stack will get the stack size ulimit size and the space between where malloc and mmap start should be about 2.7 GB. That 2.7 GB will of course by divided between malloc and mmap, but the division will be done dynamically based on whoever needs the space. Much better than the current static 1:1.7 division... -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org