From owner-freebsd-current@FreeBSD.ORG  Sat Jan 19 08:08:30 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 406D316A417;
	Sat, 19 Jan 2008 08:08:30 +0000 (UTC)
	(envelope-from jkim@FreeBSD.org)
Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162])
	by mx1.freebsd.org (Postfix) with ESMTP id E721713C45D;
	Sat, 19 Jan 2008 08:08:24 +0000 (UTC)
	(envelope-from jkim@FreeBSD.org)
Received: from niksun.com (anuket [10.70.0.5])
	by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id m0IHHto7037044;
	Fri, 18 Jan 2008 12:17:55 -0500 (EST)
	(envelope-from jkim@FreeBSD.org)
From: Jung-uk Kim <jkim@FreeBSD.org>
To: freebsd-arch@FreeBSD.org
Date: Fri, 18 Jan 2008 12:17:46 -0500
User-Agent: KMail/1.6.2
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200801181217.52788.jkim@FreeBSD.org>
X-Virus-Scanned: ClamAV 0.92/5494/Fri Jan 18 09:23:47 2008 on
	anuket.mj.niksun.com
X-Virus-Status: Clean
Cc: freebsd-current@FreeBSD.org
Subject: [RFC] SysV SHM on 64-bit platforms
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jan 2008 08:08:30 -0000

While I was working on kern/113218, I realized it is a bigger problem 
than I originally thought:

http://www.freebsd.org/cgi/query-pr.cgi?pr=113218

Because fixing this PR breaks ABI, I had to make compat shims.  But 
the question is which branch to break?  Since we are very close to 
7.0-RELEASE, the question became more complicated.  A lot of people 
are asking me to fix this PR because it is much needed fix for large 
database installations, so I have to make a quick decision. :-(

I think I have four options (with corresponding patches):

- Option 1: HEAD.

HEAD:		http://people.freebsd.org/~jkim/shmmax8o.diff

- Option 2: HEAD and RELENG_7.

HEAD:		http://people.freebsd.org/~jkim/shmmax8c2.diff
RELENG_7:	http://people.freebsd.org/~jkim/shmmax7s2.diff

- Option 3: HEAD, RELENG_7, and RELENG_7_0.

HEAD:		http://people.freebsd.org/~jkim/shmmax8c.diff
RELENG_7:	http://people.freebsd.org/~jkim/shmmax7s.diff
RELENG_7_0:	http://people.freebsd.org/~jkim/shmmax70.diff

- Option 4: Don't do anything ATM.  Break it with ipc_perm later.

FYI, fixing ipc_perm is a lot more complicated and very intrusive.

What do I do now?  Do I have any other options?

Jung-uk Kim