From: David Woodhouse <dwmw2@infradead.org>
To: "Artem B. Bityuckiy" <dedekind@infradead.org>
Cc: MTD List <linux-mtd@lists.infradead.org>
Subject: Re: JFFS3 memory consumption
Date: Wed, 26 Jan 2005 18:15:21 +0000 [thread overview]
Message-ID: <1106763322.19262.19.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0501261710570.3222@phoenix.infradead.org>
On Wed, 2005-01-26 at 17:11 +0000, Artem B. Bityuckiy wrote:
> > If you use larger "chunks" you'll get better overall compression. E.g.
> > a 64KiB node should compress better than a 4KiB node. This is partially
> > how squashfs achieves better compression that cramfs.
> Surely, but how about read degradation?
See what zisofs does. If you populate adjacent pages when decompressing,
rather than just throwing away the extra data you had to decompress
anyway, then it's not so bad.
--
dwmw2
next prev parent reply other threads:[~2005-01-26 18:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 8:44 JFFS3 memory consumption Artem B. Bityuckiy
2005-01-26 9:10 ` David Woodhouse
2005-01-26 15:57 ` Artem B. Bityuckiy
2005-01-26 17:06 ` Josh Boyer
2005-01-26 17:11 ` Artem B. Bityuckiy
2005-01-26 18:15 ` David Woodhouse [this message]
2005-01-26 18:33 ` Artem B. Bityuckiy
2005-01-26 18:55 ` David Woodhouse
2005-01-27 17:35 ` Artem B. Bityuckiy
2005-01-27 20:23 ` Thomas Gleixner
2005-01-27 22:35 ` David Woodhouse
2005-01-28 0:19 ` Thomas Gleixner
2005-01-28 0:33 ` David Woodhouse
2005-01-28 0:44 ` Thomas Gleixner
2005-01-28 8:45 ` Artem B. Bityuckiy
2005-01-28 9:03 ` Thomas Gleixner
2005-01-28 9:23 ` Artem B. Bityuckiy
2005-01-28 18:57 ` Artem B. Bityuckiy
2005-01-30 18:23 ` Artem B. Bityuckiy
2005-01-30 18:58 ` Artem B. Bityuckiy
2005-01-31 16:46 ` Jared Hulbert
2005-01-31 18:05 ` Artem B. Bityuckiy
2005-02-01 16:49 ` Thomas Gleixner
2005-02-02 15:44 ` Artem B. Bityuckiy
2005-02-02 18:34 ` Jared Hulbert
2005-02-02 19:02 ` Thomas Gleixner
2005-02-03 10:54 ` Artem B. Bityuckiy
2005-01-28 1:53 ` Josh Boyer
2005-01-28 8:50 ` 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=1106763322.19262.19.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=dedekind@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