From: Matthieu CASTET <matthieu.castet@parrot.com>
To: "dedekind1@gmail.com" <dedekind1@gmail.com>
Cc: Andi Kleen <ak@linux.intel.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 1/3] Add the snappy-c compressor to lib
Date: Wed, 9 Nov 2011 12:09:48 +0100 [thread overview]
Message-ID: <4EBA5F7C.6000506@parrot.com> (raw)
In-Reply-To: <1319978545.2126.37.camel@koala>
Hi,
Artem Bityutskiy a écrit :
> On Sun, 2011-10-30 at 14:37 +0200, Artem Bityutskiy wrote:
>> From: Andi Kleen <ak@linux.intel.com>
>>
>> This is a C port of the google snappy compressor. It has roughly
>> comparable compression to LZO, but is significantly faster on many file
>> types. For example it beats all other compressors on already
>> compressed data.
>
> Sounds cool, thanks Andi! Is any UBIFS user interested to try this out?
> I think this stuff needs some real users to make it go into mainline
> smoothly.
>
I could be interresting to have benchmarks on arm (or other system where UBIFS
is used).
snappy use lot's of unaligned access.
They need to be emulated on pre-armv6 core.
And even in newer core (armv6+), u64 unaligned access are not supported.
Matthieu
next prev parent reply other threads:[~2011-11-09 11:09 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 [this message]
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
-- 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=4EBA5F7C.6000506@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=ak@linux.intel.com \
--cc=dedekind1@gmail.com \
--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 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.