From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 8 23:12:10 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B38821065673 for ; Fri, 8 Oct 2010 23:12:10 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 7C1148FC0A for ; Fri, 8 Oct 2010 23:12:10 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.4/8.14.4) with ESMTP id o98NCAAb090211; Fri, 8 Oct 2010 16:12:10 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.4/8.14.4/Submit) id o98NCAF7090210; Fri, 8 Oct 2010 16:12:10 -0700 (PDT) (envelope-from sgk) Date: Fri, 8 Oct 2010 16:12:10 -0700 From: Steve Kargl To: Kostik Belousov Message-ID: <20101008231210.GA90183@troutmask.apl.washington.edu> References: <20101008221701.GA89977@troutmask.apl.washington.edu> <20101008222013.GT2392@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101008222013.GT2392@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.4.2.3i Cc: freebsd-amd64@freebsd.org Subject: Re: linux32 sysctl limits? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Oct 2010 23:12:10 -0000 On Sat, Oct 09, 2010 at 01:20:13AM +0300, Kostik Belousov wrote: > On Fri, Oct 08, 2010 at 03:17:01PM -0700, Steve Kargl wrote: > > 'man linux' does not list or describe the following sysctl > > variables. > > > > compat.linux32.maxvmem: 0 > > compat.linux32.maxssiz: 67108864 > > compat.linux32.maxdsiz: 536870912 > > > > Are there any limitations with setting these to > > say 1G for stack and 4G for data on a system with > > 16G of memory? > > The linux ABI processes are 32bit, so you cannot reallistically assign > 4Gb to maxdsiz. The space between data (bss) end and stack bottom is > used for mappings, so it should be kept large enough. Does this mean that maxssiz+maxdsiz=3G would allow 1G for mappings? The only linux app that will be running is matlab (and I suppose any children processes of matlab). -- Steve