Date: Mon, 28 Jan 2002 21:39:39 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: "Kenneth D. Merry" <ken@kdm.org> Cc: arch@FreeBSD.ORG Subject: Re: Geom project, limited preview... Message-ID: <47066.1012250379@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 28 Jan 2002 13:18:34 MST." <20020128131834.A4983@panzer.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20020128131834.A4983@panzer.kdm.org>, "Kenneth D. Merry" writes: [...] >This will require thought, [...] >[...] >Depending on your design, [...] I am sure you are right, but I cannot really provide you any assurance as to what can and what cannot be done yet. Between you and sos@ and me, I am sure we can cover this ground, but I have this nagging feeling that a geom module of the kind we are talking about, is composed of 10% "doing the actual I/O" and 90% "dissecting the on-disk configuration records and setting things up". I have implemented some generic code for your average "subdisk" module (BSD, MBR, SUNLABEL, MACLABEL and so on) but the actual savings is surprisingly small (the benefit in consistency is of course still more than enough to justify it). I _think_ my design and code allows for "doing anything" but I may be wrong. -- 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?47066.1012250379>