From owner-freebsd-arch@FreeBSD.ORG Wed Jan 25 06:45:05 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C90616A41F; Wed, 25 Jan 2006 06:45:05 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BDFD43D48; Wed, 25 Jan 2006 06:45:04 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [192.168.2.4]) ([10.251.60.107]) by a50.ironport.com with ESMTP; 24 Jan 2006 22:45:03 -0800 Message-ID: <43D71E6F.1010008@elischer.org> Date: Tue, 24 Jan 2006 22:45:03 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeff Roberson References: <43CD612E.2060002@elischer.org> <63333.1137536336@critter.freebsd.dk> <20060121003908.GD6017@cs.rice.edu> <43D18816.3010909@elischer.org> <20060122194739.O602@10.0.0.1> <43D4630E.70201@samsco.org> <20060124211522.D602@10.0.0.1> In-Reply-To: <20060124211522.D602@10.0.0.1> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, arch@freebsd.org, Alan Cox , Poul-Henning Kamp Subject: Re: Large virtual page size support. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2006 06:45:05 -0000 Jeff Roberson wrote: > > Thanks for the encouragement. There are a few unresolved issues. > Most importantly, how are we presently dealing with config options > that break modules? If the option is to stay as it is, modules will > have to be aware of the page size that is agreed upon by the rest of > the kernel. well we could as a matter of principal make the page size a variable and not a constant. we did the same with HZ which was always a #define. > > There other issues are mostly considering ways to reduce the impact of > the patch on the rest of the system. How to tidy it up a bit more, if > it can be. > >> >> Scott >>