From: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
To: <linux-mtd@lists.infradead.org>
Cc: <dwmw2@infradead.org>
Subject: compr_zlib.c
Date: Tue, 19 Mar 2002 19:55:21 +0100 [thread overview]
Message-ID: <004c01c1cf77$9f28e5c0$0200a8c0@telia.com> (raw)
In-Reply-To: 200203061645.g26Gjl806741@skylab.outpostsentinel.com
OK, a new compression type will be cleaner. What should be done with compression types
not supported? Can't say that I understand the logic behind the unsupported nodes.
What do you think about STREAM_END_SPACE? Should it be changed to something bigger?
What is the maximum amount of data JFFS2 will try to compress in one go? I am
thinking of adjusting windowBits and memLevel, now they default to 128 KB each which
seems a bit too much.
Will you accept a patch against the stable branch?
Also there has been a few performance improvements lately and I would like to see them in the
stable branch as well. We are using them all and no problems so far. Any chance that will
happen?
Jocke
On Tue, 19 Mar 2002, Joakim Tjernlund wrote:
> No comments so far.
> Anyone?
Looks good. Suspect we should make it a new compression type instead, and
fix the mount routine to check for compression types we don't support,
like we check for node types we don't support.
--
dwmw2
next prev parent reply other threads:[~2002-03-19 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 15:54 Lost DOC2000 after installation of Grub Chris Fowler
2002-03-06 19:18 ` Ilguiz Latypov
2002-03-19 18:55 ` Joakim Tjernlund [this message]
2002-03-20 17:36 ` compr_zlib.c David Woodhouse
2002-03-20 18:58 ` compr_zlib.c Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 12:14 Cache mappings and invalidate Joakim Tjernlund
2001-12-17 13:08 ` Burst read and other improvements Joakim Tjernlund
2002-03-11 8:56 ` compr_zlib.c Joakim Tjernlund
2002-03-19 12:03 ` compr_zlib.c Joakim Tjernlund
2002-03-19 12:24 ` compr_zlib.c David Woodhouse
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='004c01c1cf77$9f28e5c0$0200a8c0@telia.com' \
--to=joakim.tjernlund@lumentis.se \
--cc=dwmw2@infradead.org \
--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