From: David Woodhouse <dwmw2@infradead.org>
To: "Artem B. Bityuckiy" <dedekind@infradead.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [RFC] CryptoAPI & Compression
Date: Fri, 01 Apr 2005 15:44:06 +0100 [thread overview]
Message-ID: <1112366647.3899.66.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0504011534460.9305@phoenix.infradead.org>
On Fri, 2005-04-01 at 15:36 +0100, Artem B. Bityuckiy wrote:
> In our code we do zlib_deflate(stream, Z_SYNC_FLUSH), so we always flush
> the output. So the final zlib_deflate(stream, Z_FINISH) requires 1 byte
> for the EOB marker and 4 bytes for adler32 (5 bytes total). Thats all. If
> we compress a huge buffer, then we still need to output those 5 bytes as
> well. I.e, the overhead of each block *is not accumulated* ! I even need
> to make the reserved space less then 12 bytes!
Hm. Could we avoid using Z_SYNC_FLUSH and stick with a larger amount?
That would give us better compression.
--
dwmw2
next prev parent reply other threads:[~2005-04-01 14:46 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 16:08 [RFC] CryptoAPI & Compression Artem B. Bityuckiy
2005-03-26 4:44 ` Herbert Xu
2005-03-26 11:32 ` Artem B. Bityuckiy
2005-03-28 17:22 ` Artem B. Bityuckiy
2005-03-29 10:35 ` Herbert Xu
2005-03-29 11:55 ` Artem B. Bityuckiy
2005-03-31 2:19 ` Herbert Xu
2005-03-31 10:43 ` Artem B. Bityuckiy
2005-03-31 11:11 ` Herbert Xu
2005-04-01 14:36 ` Artem B. Bityuckiy
2005-04-01 14:44 ` David Woodhouse [this message]
2005-04-01 14:57 ` Artem B. Bityuckiy
2005-04-01 15:05 ` David Woodhouse
2005-04-01 15:22 ` Artem B. Bityuckiy
2005-04-01 15:33 ` Jörn Engel
2005-04-03 8:47 ` Artem B. Bityuckiy
2005-04-01 15:23 ` Herbert Xu
2005-04-01 15:41 ` Artem B. Bityuckiy
2005-04-01 22:13 ` Herbert Xu
2005-04-03 8:22 ` Artem B. Bityuckiy
2005-04-03 8:27 ` Artem B. Bityuckiy
2005-04-03 8:29 ` Artem B. Bityuckiy
2005-04-03 8:44 ` Herbert Xu
2005-04-03 8:59 ` Artem B. Bityuckiy
2005-04-03 9:30 ` Herbert Xu
2005-04-03 9:45 ` Artem B. Bityuckiy
2005-04-03 10:00 ` Herbert Xu
2005-04-03 10:06 ` David Woodhouse
2005-04-03 10:17 ` Herbert Xu
2005-04-03 10:23 ` Artem B. Bityuckiy
2005-04-03 11:42 ` Herbert Xu
2005-04-03 15:24 ` Artem B. Bityuckiy
2005-04-03 11:19 ` David Woodhouse
2005-04-03 11:40 ` Herbert Xu
[not found] ` <4250175D.5070704@yandex.ru>
[not found] ` <20050403213207.GA24462@gondor.apana.org.au>
2005-04-18 15:09 ` Artem B. Bityuckiy
2005-04-19 9:25 ` Herbert Xu
2005-04-19 12:51 ` Artem B. Bityuckiy
2005-04-19 22:10 ` Herbert Xu
2005-04-03 10:19 ` Artem B. Bityuckiy
2005-04-03 9:20 ` Artem B. Bityuckiy
2005-03-31 9:51 ` Herbert Xu
2005-04-03 11:41 ` Artem B. Bityuckiy
2005-04-03 11:47 ` Herbert Xu
2005-04-03 11:53 ` Artem B. Bityuckiy
2005-04-03 12:00 ` Herbert Xu
2005-04-03 12:01 ` Artem B. Bityuckiy
2005-04-03 12:07 ` Herbert Xu
2005-04-03 12:18 ` Artem B. Bityuckiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1112366647.3899.66.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=dedekind@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.