From owner-freebsd-arch@FreeBSD.ORG Wed May 11 10:43:28 2011 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAEAA106566B for ; Wed, 11 May 2011 10:43:28 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1FDFF8FC08 for ; Wed, 11 May 2011 10:43:27 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA01578; Wed, 11 May 2011 13:43:23 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4DCA684B.4020400@FreeBSD.org> Date: Wed, 11 May 2011 13:43:23 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110504 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Doug Rabson References: <4DC95006.1020404@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: FreeBSD Arch Subject: Re: arch-independent disks in sys/boot, libstand X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2011 10:43:28 -0000 on 11/05/2011 12:16 Doug Rabson said the following: > There is an example of this in sys/boot/zfs. The approach taken is to scan > physical drives as they appear and piece them together into ZFS pools based on the > drive metadata. The pools appear as devices in the device table and the actual ZFS > filesystem reader is built on top of that. Yes, thank you, I've seen that code. My question was not specific enough - I am interested in the things like i386_fmtdev vs other archs, i386_parsedev vs other archs, struct i386_devdesc vs other archs, etc. I.e. I would like to make ZFS representable (in some shape) via struct devdesc. But it seems that every supported arch has its own extension of struct devdesc that it uses and its own set of functions to work with that struct. Or, using another example, I'd like to be able to specify something like "zfs:/pool/fs:/boot/kernel" as a kernel name and have that work for all archs. I'd hate to duplicate code that would handle that acress all xxx_parsedev implementations for all architectures. > On 10 May 2011 10:47, Andriy Gapon > wrote: > > > I would like to ask for an advice about where/how to implement architecture > independent disk type(s) for sys/boot. The types would be logical disks built on > top of physical architecture-specific disks/partitions. Possible examples are: > ZFS pools, LVM volumes, etc. > > -- > Andriy Gapon > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org > " > > -- Andriy Gapon