From owner-freebsd-small Fri Jul 20 1: 5: 5 2001 Delivered-To: freebsd-small@freebsd.org Received: from kalaid.f2f.com.ua (kalaid.f2f.com.ua [62.149.0.33]) by hub.freebsd.org (Postfix) with ESMTP id 25B8737B405 for ; Fri, 20 Jul 2001 01:04:59 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from mail.uic-in.net (root@[212.35.189.4]) by kalaid.f2f.com.ua (8.11.4/8.11.4) with ESMTP id f6K86fO34824; Fri, 20 Jul 2001 11:06:41 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (das0-l93.uic-in.net [212.35.189.220]) by mail.uic-in.net (8.11.4/8.11.4) with ESMTP id f6K84Yk27565; Fri, 20 Jul 2001 11:04:42 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.4/8.11.3) with ESMTP id f6K84RD77977; Fri, 20 Jul 2001 11:04:27 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3B57E622.5EA768C4@FreeBSD.org> Date: Fri, 20 Jul 2001 11:04:50 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Andrew Hannam Cc: small@FreeBSD.org Subject: Re: Extending md(4) to allow it use pre-compressed disk image References: <3B52CC08.1B08210F@FreeBSD.org> <009901c11045$d0536a40$0104010a@famzon.com.au> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrew Hannam wrote: > Does this include the necessary utilities to enable it to be written into > the kernel so that the (bloated) loader is not needed in a Pico situation ? I suppose that it could be written into the kernel like any other md(4) image. The only problem in this sutuation is the fact that we need to tell md(4) driver somehow that the image is in fact compressed one, not just plain md(4) image. It is easier with loader(8), because it allows specifying type of the image (i.e. md_image vs md_image_compressed). > I would imagine that something like the "write_mfs_in_kernel" utility. You > may also need some pre-compression utility so that you know how much space > to allocate into the kernel image when building the kernel. The write_mfs_in_kernel utility should work w/o problems with compressed image, however it is necessary to create an image before compiling the kernel to estimate size that needs to be allocated. -Maxim > ----- Original Message ----- > From: "Maxim Sobolev" > To: > Cc: > Sent: Monday, July 16, 2001 9:12 PM > Subject: Extending md(4) to allow it use pre-compressed disk image > > > Hi folks, > > > > I extended md(4) driver to allow it use pre-compressed disk image. In > > contrast with the current implementation, when loader(8) on loading > > decompresses compressed image and holds it uncompressed in the memory, > > with new feature loader(8) places compressed image into a memory, > > while md(4) decompresses sectors when they are read. This could be > > useful to decrease minimal memory requrements on FreeBSD install or in > > another cases when memory is scarce. Performance is quite good - even > > P133 reads data from such device at 2-2.5MB/s. > > > > Since standard gzip format is not really suitable for the task I > > created an utility that splits original image into clusters (cluster > > size could vary), compresses each cluster using zlib and writes > > compressed clusters along with information about offset of each > > cluster into resulting image. After that compressed image could be put > > into the floppy or other media, loaded using loader(8) and accessed > > through md(4) as usually. The only difference is that it is impossible > > to write into resulting disk. > > > > I would like to know if there is enough interest in integrating this > > feature into base system, please let me know what do you think about > > it. > > > > -Maxim > > P.S. Please keep me on the CC list. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-small" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message