From owner-freebsd-arch Wed Mar 21 13:25:20 2001 Delivered-To: freebsd-arch@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0D04937B71C; Wed, 21 Mar 2001 13:25:18 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA11358; Wed, 21 Mar 2001 13:25:22 -0800 Date: Wed, 21 Mar 2001 13:25:17 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: arch@FreeBSD.ORG Subject: Re: remind me again, why is MAXPHYS only 128k ? In-Reply-To: <88825.985208451@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks complained about some VM issues for trying to wire down a megabyte, etc. You sent me a suggestion as to how we could do specific device wiring w/o increasing MAXPHYS itself. That said, in NetBSD I've run 1024K MAXPHYS- you just have to make sure that the max buffer size doesn't track MAXPHYS 'coz you run out of memory rather quick. > > Are there any roadblocks for increasing MAXPHYS as a tweakable these > days, or is it still an "do not alter or ELSE..." #define ? > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message