From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Yann Collet <yann.collet.73@gmail.com>
Cc: Kyungsik Lee <kyungsik.lee@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Chanho Min <chanho.min@lge.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: lz4 improvements backporting from official repository
Date: Fri, 28 Feb 2014 23:32:08 +0300 [thread overview]
Message-ID: <20140228203208.GA2248@swordfish> (raw)
Hello,
Sorry if it's been discussed a number of times already.
Currently used LZ4 compression implementation based on svn revision r90
(at least this is what commit c72ac7a1a926 "lib: add lz4 compressor module"
says) from 3rd party repository: http://lz4.googlecode.com/svn/trunk/
I just checked out that repository and lz4 now on revision r113. The svn log
shows that there have been a number of performance improvements and fixes,
e.g.
------------------------------------------------------------------------
r113 | yann.collet.73@gmail.com | 2014-02-04 17:11:10 +0300 (Tue, 04 Feb 2014) | 5 lines
Large decompression speed improvement for GCC 32-bits. Thanks to Valery Croizier !
LZ4HC : Compression Level is now a programmable parameter (CLI from 4 to 9)
Separated IO routines from command line (lz4io.c)
Version number into lz4.h (suggested by Francesc Alted)
[..]
------------------------------------------------------------------------
r101 | yann.collet.73@gmail.com | 2013-08-12 11:35:52 +0300 (Mon, 12 Aug
2013) | 9 lines
Removed dependency to "lz4_encoder.h" and "lz4hc_encoder.h"
Improved speed of LZ4_decompress_fast() with GCC
Improved speed of LZ4_decompress_safe() for 32-bits
Made the fast LZ4 compression compatible with low-memory systems (buffer
address < 64K). Thanks Francois Gretief for report and suggestion.
[..]
and so on.
I wonder does anybody keep an eye on that improvements? Is there any
'standard' procedure of backporting/cherry-picking commits from 3rd party
repositories?
thanks,
-ss
reply other threads:[~2014-02-28 20:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140228203208.GA2248@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chanho.min@lge.com \
--cc=kyungsik.lee@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yann.collet.73@gmail.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.