From owner-cvs-all Sun Jan 26 22:49:12 2003 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 605AF37B406 for ; Sun, 26 Jan 2003 22:49:11 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 359C743F6D for ; Sun, 26 Jan 2003 22:49:10 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 84370 invoked by uid 1000); 27 Jan 2003 06:49:12 -0000 Date: Sun, 26 Jan 2003 22:49:12 -0800 (PST) From: Nate Lawson To: phk@freebsd.org Cc: cvs-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sbin/disklabel disklabel.c In-Reply-To: <15853.1043649348@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 27 Jan 2003 phk@freebsd.org wrote: > In message , Nate Lawson wri > tes: > >I'm not sure why boot block/disk label writes can't be done as ordinary > >writes and semantic checking performed by whichever GEOM layer thinks it > >knows best about that portion of a disk. What is wrong with that > >approach? > > It doesn't work without running a lot of special-case testing code, > possibly several times, on each and every disk I/O request. I thought GEOM would (eventually) support providers registering for byte ranges of the same device. For example: geom_i386mbr: 0-511 (parse PC mbr) geom_label: 512-8k (parse bsd label) All requests that were for other ranges would bypass these providers, making it unnecessary to run any special case code for most requests. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message