From owner-freebsd-current@FreeBSD.ORG Wed May 25 19:39:34 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0764216A41C for ; Wed, 25 May 2005 19:39:34 +0000 (GMT) (envelope-from csjp@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5CC343D4C for ; Wed, 25 May 2005 19:39:33 +0000 (GMT) (envelope-from csjp@FreeBSD.org) Received: from freefall.freebsd.org (csjp@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j4PJdX3i033287 for ; Wed, 25 May 2005 19:39:33 GMT (envelope-from csjp@freefall.freebsd.org) Received: (from csjp@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j4PJdXZi033286 for freebsd-current@FreeBSD.org; Wed, 25 May 2005 19:39:33 GMT (envelope-from csjp) Date: Wed, 25 May 2005 19:39:33 +0000 From: "Christian S.J. Peron" To: freebsd-current@FreeBSD.org Message-ID: <20050525193933.GA32095@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: [patch] 2Gb SYSVSHM limitation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2005 19:39:34 -0000 I am looking for a review and testers for a fix to the 2 Gig memory limitation when allocating system V shared memory segments. A couple of notes: 1) This patch breaks ABI because it changes the size of the shminfo structure. This means that ipcs will need to be recompiled. (and anything else which uses struct shminfo). 2) Because this changes the size limitations stored in struct shminfo from a signed integer to an unsigned long, it allows x86 to allocate up to 4 gigs and also allows 64 bit architectures to do far more. Even though the size parameter used by shmget(2) is a size_t, the upper size limit is currently stored in a signed int. Limiting the maximum size of an allocation to 2147483647 bytes. Patch can be downloaded from: http://people.freebsd.org/~csjp/bigsharedmem.1117028863.diff Should apply to any recent version of -CURRENT cleanly. Thanks! -- Christian S.J. Peron csjp@FreeBSD.ORG FreeBSD Committer