Date: Mon, 19 Jan 2004 20:54:08 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Max Khon <fjoe@iclub.nsu.ru> Cc: freebsd-current@freebsd.org Subject: Re: read-only compressed fs (call for testers) Message-ID: <98092.1074542048@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 20 Jan 2004 00:29:55 %2B0600." <20040119182955.GA60760@iclub.nsu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20040119182955.GA60760@iclub.nsu.ru>, Max Khon writes: >Hello! > >I have seen some requests for read-only compressed fs support recently. >Last weekend I had a few spare cycles and implemented GEOM class that >allows to use cloop V2.0 (compressed loopback device for Linux) fs images. > >More details, tarballs with geom_ugz and a port for tools needed >to create/extract compressed fs images are available at >http://people.freebsd.org/~fjoe/geom_ugz/ I quickly glanced at this: The one thing which stuck in my mind is that for performance reasons running inflate in the "up" geom path may be wrong. Doing CPU intensive stuff in the "up" and "down" paths is generally a bad idea and should be avoided because it will hold up other disk-trafic while the CPU chews. In GBDE I stuck all the crypto off to a kthread for this reason. In this case it may be a valid trade-off, I can't tell, just keep it in mind down the road. Ohh, Have I told anyone how positively delighted I am to see people grow GEOM classes all the places ? Wheeeeeeee! :-> Poul-Henning -- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?98092.1074542048>