Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262759AbVDAPmz (ORCPT ); Fri, 1 Apr 2005 10:42:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262774AbVDAPmz (ORCPT ); Fri, 1 Apr 2005 10:42:55 -0500 Received: from phoenix.infradead.org ([81.187.226.98]:27147 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S262759AbVDAPmL (ORCPT ); Fri, 1 Apr 2005 10:42:11 -0500 Date: Fri, 1 Apr 2005 16:41:44 +0100 (BST) From: "Artem B. Bityuckiy" To: Herbert Xu cc: dwmw2@infradead.org, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org Subject: Re: [RFC] CryptoAPI & Compression In-Reply-To: <20050401152325.GB4150@gondor.apana.org.au> Message-ID: References: <20050401152325.GB4150@gondor.apana.org.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-SRS-Rewrite: SMTP reverse-path rewritten from by phoenix.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1126 Lines: 26 > I thought stored blocks (incompressible blocks) were limited to 64K > in size, no? Blocks are limited in size by 64K, true. But why it matters for us? Suppose we compress 1 GiB of input, and have a 70K output buffer. We reserve 5 bytes at the end and start calling zlib_deflate(stream, Z_SYNCK_FLUSH) recurrently. It puts one 64K block, puts its end marker, then puts a part of a second block. Then we call zlib_deflate(strem, Z_FINISH) and it puts the end marker of the second block and the adler32 checksum of the entire stream. So I don't see any problem albeit I didn't try yet :-) But I'll do. > Please double check zlib_deflate/deflate.c and > zlib_deflate/deftree.c. Surely I'll check. I'll even test the new implementation (which I didn't actually do) with a large input before sending it next time. -- Best Regards, Artem B. Bityuckiy, St.-Petersburg, Russia. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/