From owner-freebsd-arch Wed Mar 21 13:46:31 2001 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 8DF5837B71B; Wed, 21 Mar 2001 13:46:27 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f2LLkF189601; Wed, 21 Mar 2001 22:46:15 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matt Dillon Cc: Mike Smith , arch@FreeBSD.ORG Subject: Re: remind me again, why is MAXPHYS only 128k ? In-Reply-To: Your message of "Wed, 21 Mar 2001 13:38:08 PST." <200103212138.f2LLc8a21690@earth.backplane.com> Date: Wed, 21 Mar 2001 22:46:15 +0100 Message-ID: <89599.985211175@critter> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200103212138.f2LLc8a21690@earth.backplane.com>, Matt Dillon writes: > In anycase, my suggestion would be to leave it alone and instead work on > optimizing the RAW DEVICE I/O path to not be limited by MAXPHYS at all. > Increasing it to 256K might be possible, but increasing it to 1MB is > out of the question (insofar as being a default). Well, that is stuck on the b_pages field in the (p)buf's. I was wondering if we should make that a ** instead of a *[] so that it could be sized dynamically for pbufs. Hmm.... -- 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