From owner-freebsd-current@FreeBSD.ORG Wed Sep 2 15:47:03 2009 Return-Path: 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 DAC8A106566C for ; Wed, 2 Sep 2009 15:47:03 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 5A7048FC15 for ; Wed, 2 Sep 2009 15:47:03 +0000 (UTC) Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 253265031; Wed, 02 Sep 2009 18:46:59 +0300 Message-ID: <4A9E9366.9050601@FreeBSD.org> Date: Wed, 02 Sep 2009 18:46:46 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20090901) MIME-Version: 1.0 To: Mel Flynn References: <4A9E8677.1020208@FreeBSD.org> <200909021728.21566.mel.flynn+fbsd.current@mailing.thruhere.net> In-Reply-To: <200909021728.21566.mel.flynn+fbsd.current@mailing.thruhere.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Derek \(freebsd lists\)" <482254ac@razorfever.net>, freebsd-current@freebsd.org Subject: Re: MAXPHYS and physical memory (Was: Re: siis/atacam/ata/gmirror 8.0-BETA3 disk performance) 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, 02 Sep 2009 15:47:03 -0000 Mel Flynn wrote: > On Wednesday 02 September 2009 16:51:35 Alexander Motin wrote: > >> For maximum linear I/O performance you may want to build kernel with >> options MAXPHYS=(1024*1024) > > I've found that just doubling the default MAXPHYS already panics-on-boot a > 1.5GB i386 system. Is there any reasonable conversion table for MAXPHYS to > physical memory, since various memory related kernel setups are derived from > or calculated with MAXPHYS? What especially your panic was about? It could be bug in ATA(4) or some other code, that does not handle MAXPHYS correctly. I don't think that you could reach memory limit during simple system boot because of that. I am successfully running my testing Pentium-75 with 64MB RAM with 1MB MAXPHYS. Could you show your panic message? -- Alexander Motin