From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Mike Dunn <mikedunn@newsguy.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH 1/3] Add the snappy-c compressor to lib
Date: Tue, 22 Nov 2011 18:23:44 +0100 [thread overview]
Message-ID: <4ECBDAA0.6010105@parrot.com> (raw)
In-Reply-To: <20111122163749.GH6624@sirena.org.uk>
Mark Brown a écrit :
> On Thu, Nov 17, 2011 at 11:36:17PM +0200, Artem Bityutskiy wrote:
>
>> Yeah, of course it would be interesting to see. If snappy is a win-win
>> on ARM, we should merge it.
>
> It might be interesting to use it for the compressed cache type in regmap
> as well.
>
For info we did some bench mark on omap3 (cortexa-8) for decompressing
hibernation image.
And snappy was a lose-lose against lzf (bigger compressed result, slower to
decompress) :
algo : compressed size , time to decompress
snappy (16 and 32 bits unaligned access done by hardware) : 45Mo, 3.5 s
snappy (unaligned access done by software) : 45Mo, 2.50 s
lzf (unalign access done by softare) : 40Mo, 2.35 s
Of course this is against one pattern (hibernation image) and benchmark should
be done on other patterns.
Matthieu
next prev parent reply other threads:[~2011-11-22 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-30 12:37 [PATCH 1/3] Add the snappy-c compressor to lib Artem Bityutskiy
2011-10-30 12:42 ` Artem Bityutskiy
2011-11-09 11:09 ` Matthieu CASTET
2011-11-09 13:06 ` Mike Dunn
2011-11-17 21:36 ` Artem Bityutskiy
2011-11-22 16:37 ` Mark Brown
2011-11-22 17:23 ` Matthieu CASTET [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-20 23:38 Andi Kleen
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=4ECBDAA0.6010105@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mikedunn@newsguy.com \
/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.