From owner-freebsd-small Mon Nov 29 15: 7: 1 1999 Delivered-To: freebsd-small@freebsd.org Received: from gta.com (mailgate.gta.com [199.120.225.4]) by hub.freebsd.org (Postfix) with ESMTP id F1784154D5 for ; Mon, 29 Nov 1999 15:06:56 -0800 (PST) (envelope-from lab@gta.com) Received: from gta.com (GTA internal mail system) by gta.com id SAA88340; Mon, 29 Nov 1999 18:10:23 -0500 (EST) Date: Mon, 29 Nov 1999 18:10:23 -0500 (EST) From: Larry Baird Message-Id: <199911292310.SAA88340@gta.com> To: freebsd-small@freebsd.org Subject: Re: md - memory disk wishlist ? In-Reply-To: <23112.943907996@critter.freebsd.dk> Organization: Global Technology Associates, Inc. User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.3-STABLE (i386)) Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <23112.943907996@critter.freebsd.dk> you wrote: > I'm looking for input from this crowd: what features do you want to > see from the md driver ? > Currently it supports two modes of operation: > 1. Preloaded images. This is like MFS_ROOT basically, > but you can muliple images and get multiple devices. Can you shed a little bit of light on how md(4) works as compared to MFS_ROOT? Is there some documentation somewhere that I missed? Is there a utility similar to write_mfs_in_kernel? > 2. Malloc mode. Here storage is malloc(9)'ed on as needed > basis and freed back when possible (with UFS for instance). > Simple compression is performed: if a sector have all bytes > identical no storage will be alocated, only that byte value > will be stored. Does malloc mode also apply to preloaded images? > I would like to hear from the embedded people what you need from a > memory device driver in FreeBSD in the future. I'll give this some thought. -- ------------------------------------------------------------------------ Larry Baird Global Technology Associates, Inc. | Orlando, FL Email: lab@gta.com | TEL 407-380-0220, FAX 407-380-6080 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message