Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753924AbXFKULs (ORCPT ); Mon, 11 Jun 2007 16:11:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751479AbXFKULi (ORCPT ); Mon, 11 Jun 2007 16:11:38 -0400 Received: from smtpq2.groni1.gr.home.nl ([213.51.130.201]:53182 "EHLO smtpq2.groni1.gr.home.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750990AbXFKULh (ORCPT ); Mon, 11 Jun 2007 16:11:37 -0400 Message-ID: <466DAB95.2040909@gmail.com> Date: Mon, 11 Jun 2007 22:07:49 +0200 From: Rene Herman User-Agent: Thunderbird 1.5.0.12 (X11/20070509) MIME-Version: 1.0 To: Dave Jones , Jan Engelhardt , "H. Peter Anvin" , Andrew Morton , Andy Whitcroft , Steve Fox , Mel Gorman , linux-kernel@vger.kernel.org Subject: Re: [PATCH] move the kernel to 16MB for NUMA-Q References: <466D550C.4030600@shadowen.org> <63a08cc7547f14065becdf9a94d0d529@pinky> <20070611091558.f468f205.akpm@linux-foundation.org> <20070611172006.GI9174@redhat.com> <466D882D.70001@zytor.com> <20070611184621.GA25371@redhat.com> In-Reply-To: <20070611184621.GA25371@redhat.com> Content-Type: multipart/mixed; boundary="------------050309040204070909060000" X-AtHome-MailScanner-Information: Please contact support@home.nl for more information X-AtHome-MailScanner: Found to be clean Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3720 Lines: 114 This is a multi-part message in MIME format. --------------050309040204070909060000 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit On 06/11/2007 08:46 PM, Dave Jones wrote: > On Mon, Jun 11, 2007 at 08:19:57PM +0200, Jan Engelhardt wrote: > > > > On Jun 11 2007 10:36, H. Peter Anvin wrote: > > > > > >Picking the 16 MB base is a bit obnoxious on small-memory machines, 4 MB > > >would probably be a more reasonable base. Of course, 16 MB would avoid > > >the issue of the handful of machines with memory holes at 15-16 MB. > > > > How will this work at all with a 5 MB machine? > > Unless you're running with a bunch of CONFIG_EMBEDDED options enabled, > and a seriously pared down (almost to the point of uselessness) > userspace, you may have already lost. > > Do such beasts even exist ? My memories of low-memory x86en I had > only allowed power of 2 memory sizes. I have a 386 here that allows 5M, with 4x256K in bank 0 and 4x1M in bank 1 (it has 16M). 4M, let alone 16, wouldn't work on a 5M machine ofcourse. But, it's just a default anyway. Would it be considered beneficial to more explicitly provide a few options through a config menu, something like the attached? I don't know how to also (cleanly) provide a custom value in addition to the choices in Kconfig but maybe more options are not actually considered useful anyway? And perhaps it's not considered useful period. Please just drop on the floor if so. Rene. --------------050309040204070909060000 Content-Type: text/plain; name="physical_start.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="physical_start.diff" diff --git a/arch/i386/Kconfig b/arch/i386/Kconfig index 8770a5d..6737529 100644 --- a/arch/i386/Kconfig +++ b/arch/i386/Kconfig @@ -813,9 +813,10 @@ config CRASH_DUMP PHYSICAL_START. For more details see Documentation/kdump/kdump.txt -config PHYSICAL_START - hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP) - default "0x100000" +choice + depends on EMBEDDED || CRASH_DUMP + prompt "Physical address where the kernel is loaded" + default PHYSICAL_START_1M help This gives the physical address where the kernel is loaded. @@ -854,6 +855,40 @@ config PHYSICAL_START Don't change this unless you know what you are doing. + config PHYSICAL_START_1M + bool "1M" + help + Choose this to load the kernel at the standard 1M address. + + config PHYSICAL_START_4M + bool "4M" + help + Loading the kernel at a 4M aligned physical address can + make for a slightly faster kernel. + + Choose this if you have 8M or more installed. + + config PHYSICAL_START_16M + bool "16M" + help + Loading the kernel at a 4M aligned physical address can + make for a slightly faster kernel. + + Additionally, loading it at 16M gets it out of the legacy + DMA zone which you might consider beneficial if you use + devices doing legacy DMA (such as a floppy drive, an ECP + parallel port or DMA capable ISA peripherals). + + Choose this if you have 20M or more installed and a need + for legacy DMA. +endchoice + +config PHYSICAL_START + hex + default "0x100000" if PHYSICAL_START_1M + default "0x400000" if PHYSICAL_START_4M + default "0x1000000" if PHYSICAL_START_16M + config RELOCATABLE bool "Build a relocatable kernel(EXPERIMENTAL)" depends on EXPERIMENTAL --------------050309040204070909060000-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/