From: Artem Bityutskiy <dedekind1@gmail.com>
To: Mike Dunn <mikedunn@newsguy.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/3] Add the snappy-c compressor to lib
Date: Thu, 17 Nov 2011 23:36:17 +0200 [thread overview]
Message-ID: <1321565780.2272.12.camel@koala> (raw)
In-Reply-To: <4EBA7AC3.4080205@newsguy.com>
On Wed, 2011-11-09 at 05:06 -0800, Mike Dunn wrote:
> On 11/09/2011 03:09 AM, Matthieu CASTET wrote:
> >> On Sun, 2011-10-30 at 14:37 +0200, Artem Bityutskiy wrote:
> >>> 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.
>
>
> I'm currently testing ubifs on armv5 (xscale). If you'd like me to collect some
> benchmark data, I'd be glad to help if you can provide a little guidance.
Yeah, of course it would be interesting to see. If snappy is a win-win
on ARM, we should merge it.
Artem.
next prev parent reply other threads:[~2011-11-17 21:36 UTC|newest]
Thread overview: 7+ 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 [this message]
2011-11-22 16:37 ` Mark Brown
2011-11-22 17:23 ` Matthieu CASTET
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=1321565780.2272.12.camel@koala \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox