From: Richard Purdie <rpurdie@openedhand.com>
To: LKML <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
herbert@gondor.apana.org.au
Cc: linux-mtd <linux-mtd@lists.infradead.org>, linux-crypto@vger.kernel.org
Subject: [PATCH 0/5] Add LZO Compression
Date: Tue, 01 May 2007 15:46:34 +0100 [thread overview]
Message-ID: <1178030794.5883.50.camel@localhost.localdomain> (raw)
The following patch series adds LZO compression support to the kernel
and exposes it in a variety of places (jffs2, crypto).
Its a resend of a previous posted series, rediffed against recent
kernels with the couple of minors issues raised by David Woodhouse
addressed.
This patch series is also available as:
git://git.o-hand.com/linux-rpurdie linux-rpurdie-lzo
(http://git.o-hand.com/?p=linux-rpurdie;a=shortlog;h=linux-rpurdie-lzo)
LZO compression is particularly useful for jffs2 where significant boot
time speedups (~10%) and file read speed improvements (~40%) are seen
when its used with only a slight drop in file compression ratio.
It also adds a favourlzo mode to jffs2 which is similar to the existing
size mode but lets lzo compression win if the lzo compressed size is
"similar" to but not the best compression ratio. This means we can keep
zlib compression where it makes a significant difference to compressed
file size.
The final jffs2 patch which starts adding sysfs support for control of
jffs2 options at runtime that are currently available only at boottime.
There are several other controls which it may be desirable to add to the
basic framework this patch creates in due course.
Richard
next reply other threads:[~2007-05-01 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 14:46 Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-04 11:30 [PATCH 0/5] Add LZO Compression Richard Purdie
2007-02-28 19:13 Richard Purdie
2007-02-28 19:43 ` Artem Bityutskiy
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=1178030794.5883.50.camel@localhost.localdomain \
--to=rpurdie@openedhand.com \
--cc=dwmw2@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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