From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BjJKJ-0005w4-KX for qemu-devel@nongnu.org; Sat, 10 Jul 2004 10:59:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BjJKI-0005vs-4c for qemu-devel@nongnu.org; Sat, 10 Jul 2004 10:59:43 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BjJKI-0005vp-2W for qemu-devel@nongnu.org; Sat, 10 Jul 2004 10:59:42 -0400 Received: from [193.252.22.28] (helo=mwinf0304.wanadoo.fr) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BjJHd-0005C3-St for qemu-devel@nongnu.org; Sat, 10 Jul 2004 10:56:58 -0400 Received: from bellard.org (ATuileries-112-1-4-169.w81-53.abo.wanadoo.fr [81.53.133.169]) by mwinf0304.wanadoo.fr (SMTP Server) with ESMTP id 24BA2A804149 for ; Sat, 10 Jul 2004 16:56:57 +0200 (CEST) Message-ID: <40F003BE.8030200@bellard.org> Date: Sat, 10 Jul 2004 16:57:02 +0200 From: Fabrice Bellard MIME-Version: 1.0 Subject: Re: [Qemu-devel] RFC for new features References: <40EFEADE.40902@bellard.org> <40EFF718.7020304@bellard.org> <1089470834.59382.218.camel@pcgem.rdg.cyberkinetica.com> In-Reply-To: <1089470834.59382.218.camel@pcgem.rdg.cyberkinetica.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Antony T Curtis wrote: > On Sat, 2004-07-10 at 15:03, Fabrice Bellard wrote: > >>About the new features: none of them will be for the upcoming 0.6.0 >>release. Maybe for 0.6.1. >> >>Some comments: >> >>- The old console will still be available with a command line option. > > > Cool, > > >>- The disk images will support both free sector compression (as cow >>images) and "read-only" zlib based block compression, so that the >>FreeOSZoo disk images do not need to be decompressed. QEMU itself will >>never store compressed blocks as it is more complicated and less useful. > > > How about lzo compression? It is vary fast for compression and > decompression and doesn't require much memory to operate. I just want that downloaded images can be easily used. Compression for writing is less useful because hard disks are big enough, so it won't be available in the first implementation. I agree that LZO would be a good choice for a read/write compression system. Fabrice.