From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264609AbTDZFDu (ORCPT ); Sat, 26 Apr 2003 01:03:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264614AbTDZFDu (ORCPT ); Sat, 26 Apr 2003 01:03:50 -0400 Received: from franka.aracnet.com ([216.99.193.44]:35531 "EHLO franka.aracnet.com") by vger.kernel.org with ESMTP id S264609AbTDZFDt (ORCPT ); Sat, 26 Apr 2003 01:03:49 -0400 Date: Fri, 25 Apr 2003 22:15:56 -0700 From: "Martin J. Bligh" To: Hugh Dickins cc: Timothy Miller , "H. Peter Anvin" , linux-kernel@vger.kernel.org Subject: Re: TASK_UNMAPPED_BASE & stack location Message-ID: <13080000.1051334155@[10.10.2.4]> In-Reply-To: References: X-Mailer: Mulberry/2.2.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >> >> 128Mb of it? The bottom page, or even a few Mb, sure ... >> >> but 128Mb seems somewhat excessive .. > > Yes. > >> > Considering that your process space is 4gig, and that that 128Mb >> > doesn't really exist anywhere (no RAM, no page table entries, >> > nothing), it's really not excessive. >> >> I need the virtual space. > > Plus you would (very often) get more physical. i386 ELF text typically > begins at 0x08048000: putting stack just below text in many cases shares > page table between stack+text+data, and saves the page table at top of > user address space. A fine point - I hadn't thought of that. It just seems tidier all around .... M.