Herbert Xu wrote:
This relies on implementation details within zlib_deflate, which may or may not be the case. It should be easy to test though. Just write a user-space program which does exactly this and feed it something from /dev/urandom.
Well, Herbert, you're right. In case of non-compressible data things are bad. I'll continue investigating this. -- 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/
- References:
- Re: [RFC] CryptoAPI & Compression
- From: Herbert Xu <[email protected]>
- Re: [RFC] CryptoAPI & Compression
- From: "Artem B. Bityuckiy" <[email protected]>
- Re: [RFC] CryptoAPI & Compression
- From: Herbert Xu <[email protected]>
- Re: [RFC] CryptoAPI & Compression
- From: "Artem B. Bityuckiy" <[email protected]>
- Re: [RFC] CryptoAPI & Compression
- From: Herbert Xu <[email protected]>
- Re: [RFC] CryptoAPI & Compression
- From: "Artem B. Bityuckiy" <[email protected]>
- Re: [RFC] CryptoAPI & Compression
- From: Herbert Xu <[email protected]>
- Re: [RFC] CryptoAPI & Compression
- From: David Woodhouse <[email protected]>
- Re: [RFC] CryptoAPI & Compression
- From: Herbert Xu <[email protected]>
- Re: [RFC] CryptoAPI & Compression
- From: "Artem B. Bityuckiy" <[email protected]>
- Re: [RFC] CryptoAPI & Compression
- From: Herbert Xu <[email protected]>
- Re: [RFC] CryptoAPI & Compression
- Prev by Date: Re: [patch] sched: auto-tune migration costs [was: Re: Industry db benchmark result on recent 2.6 kernels]
- Next by Date: Re: sched /HT processor
- Previous by thread: Re: [RFC] CryptoAPI & Compression
- Next by thread: Re: [RFC] CryptoAPI & Compression
- Index(es):
 |