From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Joakim Tjernlund <joakim.tjernlund@lumentis.se>
Cc: linux-mtd@lists.infradead.org
Cc: David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH RFC] 1/2 central workspace for zlib
Date: Mon, 2 Jun 2003 15:32:06 +0200 [thread overview]
Message-ID: <20030602133206.GA21902@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <IGEFJKJNHJDCBKALBJLLMEBAFNAA.joakim.tjernlund@lumentis.se>
On Mon, 2 June 2003 15:03:52 +0200, Joakim Tjernlund wrote:
> >
> > The kernel workspace #defines MAX_MEM_LEVEL to 9, while the zlib
> > default is 8. That translates to 256k instead of 128k is is likely
> > pointless for JFFS2 style of compression. Another 50k come from the
> > seperate workspaces for inflate and deflate. So JFFS2 should be able
> > to work with 280k, roughly.
>
> hmm, won't the mem level in zlib_deflateInit() influence the needed workspace? I always
> figured that the memory reuirements listed in zconf.h was worst case.
> Since JFFS2 uses mem level 3, is it not possible that JFFS2 needs less memory?
Yes, that makes sense. Seems a bit hard to exploit that in a clean
way, but not impossible.
> > Have you ever seen/done benchmarks that test zlib compression
> > efficiency?
> no, sorry.
Then someone will have to do those and figure out who actually profits
from the larger mem level. Depending on the results, we could #define
the value back to 8, make it an option under CONFIG_EMBEDDED or
something similar.
Jörn
--
A surrounded army must be given a way out.
-- Sun Tzu
next prev parent reply other threads:[~2003-06-02 13:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 14:49 [PATCH RFC] 1/2 central workspace for zlib Jörn Engel
2003-05-30 15:29 ` James Morris
2003-05-30 17:43 ` Jörn Engel
2003-05-31 0:14 ` David S. Miller
2003-05-31 6:48 ` Jörn Engel
2003-05-31 6:55 ` David S. Miller
2003-05-31 7:56 ` Jörn Engel
2003-05-31 7:59 ` David S. Miller
2003-05-31 8:11 ` Jörn Engel
2003-05-31 8:12 ` David S. Miller
2003-05-31 8:22 ` Con Kolivas
2003-06-01 1:25 ` Matt Mackall
2003-06-02 12:19 ` Jörn Engel
2003-05-31 9:09 ` Arjan van de Ven
2003-05-31 6:20 ` David S. Miller
2003-05-31 10:51 ` James Morris
2003-05-31 11:07 ` Jörn Engel
2003-05-31 15:44 ` Joakim Tjernlund
2003-06-02 12:26 ` Jörn Engel
2003-06-02 13:03 ` Joakim Tjernlund
2003-06-02 13:32 ` Jörn Engel [this message]
2003-06-02 15:15 ` matsunaga
2003-06-02 15:36 ` Jörn Engel
2003-06-02 15:40 ` David Woodhouse
2003-06-02 15:53 ` Jörn Engel
2003-06-02 15:59 ` David Woodhouse
2003-06-02 16:37 ` Jörn Engel
2003-06-02 19:36 ` David Woodhouse
2003-06-02 20:54 ` Jörn Engel
2003-06-02 16:07 ` matsunaga
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=20030602133206.GA21902@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=joakim.tjernlund@lumentis.se \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox