Re: [RFC] CryptoAPI & Compression

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

 



David Woodhouse wrote:
Hm. Could we avoid using Z_SYNC_FLUSH and stick with a larger amount?
That would give us better compression.

Yes, the compression will be better. But the implementation will be more complicated. We can try to use the "bound" functions to predict how many bytes to pass to the deflate's input, but there is no guarantee they'll fit into the output buffer. In this case we'll need to try again.

Possibly, we may do something like this:

Try good compression using the prediction technique.
If we didn't fit the output buffer, use the old but determined algorithm.

--
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