From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 23 20:32:26 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F5E9106564A; Mon, 23 Feb 2009 20:32:26 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mx1.freebsd.org (Postfix) with ESMTP id 001808FC17; Mon, 23 Feb 2009 20:32:25 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from vanquish.ws.pitbpa0.priv.collaborativefusion.com (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTPSA id 9A6ABEBC0A; Mon, 23 Feb 2009 15:16:12 -0500 (EST) Date: Mon, 23 Feb 2009 15:16:11 -0500 From: Bill Moran To: Christian Peron Message-Id: <20090223151611.af79586c.wmoran@potentialtech.com> In-Reply-To: <20090223201217.GA35374@jnz.sqrt.ca> References: <1235404207.31655.2085.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> <20090223190828.GA34866@jnz.sqrt.ca> <78AACD88-3F94-4B39-9122-9C4199DFFDBA@gmail.com> <20090223201217.GA35374@jnz.sqrt.ca> X-Mailer: Sylpheed 2.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 23 Feb 2009 20:42:20 +0000 Cc: Kirk Strauser , Garrett Cooper , "Brian A. Seklecki" , freebsd-hackers@freebsd.org Subject: Re: shmmax tops out at 2G? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2009 20:32:26 -0000 In response to Christian Peron : > On Mon, Feb 23, 2009 at 11:58:09AM -0800, Garrett Cooper wrote: > [..] > > > > Why isn't the field an unsigned int / size_t? I don't see much value > > in having the size be signed... > > No idea :) This code long predates me. It's that way because the original Sun spec for the API said so. It makes little sense to change it just to unsigned. The additional 2G it would give doesn't really solve the tuning problem on a 64G system. This is simply a spec that has become outdated by modern hardware. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/