From owner-freebsd-arch Mon Feb 5 14:37:14 2001 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 385E737B684; Mon, 5 Feb 2001 14:36:56 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f15MaqB29301; Mon, 5 Feb 2001 23:36:52 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Justin T. Gibbs" Cc: Alfred Perlstein , Randell Jesup , Matt Dillon , Matthew Jacob , Mike Smith , Dag-Erling Smorgrav , Dan Nelson , Seigo Tanimura , arch@FreeBSD.ORG Subject: Re: Bumping up {MAX,DFLT}*PHYS (was Re: Bumping up {MAX,DFL}*SIZ in i386) In-Reply-To: Your message of "Mon, 05 Feb 2001 15:24:02 MST." <200102052224.f15MO2O51248@aslan.scsiguy.com> Date: Mon, 05 Feb 2001 23:36:52 +0100 Message-ID: <29299.981412612@critter> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102052224.f15MO2O51248@aslan.scsiguy.com>, "Justin T. Gibbs" writes: >> >>It's not "a simple call". >> > >It doesn't have to be a simple call if it only occurs once on mount >and whenever a component makes an async upcall telling the system that >its state has changed (array is degraded, or perhaps commonly accessed >data has migrated to a different striping or RAID layout). I think we are talking too many different things at the same time here. The upcall I (and I belive Alfred) were discussing were happening once per I/O. The one you are talking about is obviously the one to formulate an abstract clustering preference for a device ? -- 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