Re: [RFC] CryptoAPI & Compression

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux