Date: Mon, 05 Feb 2001 23:36:52 +0100
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: Alfred Perlstein <bright@wintelcom.net>, Randell Jesup <rjesup@wgate.com>, Matt Dillon <dillon@earth.backplane.com>, Matthew Jacob <mjacob@feral.com>, Mike Smith <msmith@FreeBSD.ORG>, Dag-Erling Smorgrav <des@ofug.org>, Dan Nelson <dnelson@emsphone.com>, Seigo Tanimura <tanimura@r.dl.itc.u-tokyo.ac.jp>, arch@FreeBSD.ORG
Subject: Re: Bumping up {MAX,DFLT}*PHYS (was Re: Bumping up {MAX,DFL}*SIZ in i386)
Message-ID: <29299.981412612@critter>
In-Reply-To: Your message of "Mon, 05 Feb 2001 15:24:02 MST." <200102052224.f15MO2O51248@aslan.scsiguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?29299.981412612>