From: Andi Kleen <andi@firstfloor.org>
To: chris.mason@oracle.com
Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Updated btrfs/crypto snappy interface ready for merging
Date: Thu, 12 Jan 2012 16:28:47 -0800 [thread overview]
Message-ID: <1326414530-10789-1-git-send-email-andi@firstfloor.org> (raw)
Here's a slightly updated version of the BTRFS snappy interface.
snappy is a faster compression algorithm that provides similar
compression as LZO, but generally better performance.
This version has:
- Ported to latest tree
- Extensive testing and benchmarking (in its 3.0 based incarnation)
- A few cleanups
- Adds a minor performance improvement
Should be ready for pulling into the btrfs tree now.
The crypto parts have been acked by Herbert.
The following changes since commit 2485a4b610171f4e1c4ab0d053569747795c1bbe:
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input (2012-01-12 12:40:41 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc snappy
Andi Kleen (3):
Add the snappy-c compressor to lib v2
BTRFS: Add snappy support v2
Add snappy interface to crypto API
crypto/Kconfig | 9 +
crypto/Makefile | 1 +
crypto/snappy.c | 99 ++++
fs/btrfs/Kconfig | 1 +
fs/btrfs/Makefile | 2 +-
fs/btrfs/compression.c | 1 +
fs/btrfs/compression.h | 1 +
fs/btrfs/ctree.h | 9 +-
fs/btrfs/disk-io.c | 2 +
fs/btrfs/ioctl.c | 4 +
fs/btrfs/snappy.c | 432 ++++++++++++++++
fs/btrfs/super.c | 9 +-
include/linux/snappy.h | 26 +
lib/Kconfig | 6 +
lib/Makefile | 4 +
lib/snappy.c | 1300 ++++++++++++++++++++++++++++++++++++++++++++++++
16 files changed, 1901 insertions(+), 5 deletions(-)
create mode 100644 crypto/snappy.c
create mode 100644 fs/btrfs/snappy.c
create mode 100644 include/linux/snappy.h
create mode 100644 lib/snappy.c
-Andi
next reply other threads:[~2012-01-13 0:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 0:28 Andi Kleen [this message]
2012-01-13 0:28 ` [PATCH 1/3] Add the snappy-c compressor to lib v2 Andi Kleen
2012-02-14 4:29 ` Mitch Harder
2012-02-14 19:52 ` Andi Kleen
2012-02-15 0:43 ` Mitch Harder
2012-01-13 0:28 ` [PATCH 2/3] BTRFS: Add snappy support v2 Andi Kleen
2012-01-13 0:28 ` [PATCH 3/3] Add snappy interface to crypto API Andi Kleen
2012-01-13 2:40 ` Updated btrfs/crypto snappy interface ready for merging Jaromir Zdrazil
2012-01-16 13:54 ` Chris Mason
2012-01-17 8:44 ` Li Zefan
2012-01-17 8:46 ` Andi Kleen
2012-01-17 8:56 ` Li Zefan
2012-01-17 9:27 ` Li Zefan
2012-01-17 9:51 ` Andi Kleen
2012-01-17 9:07 ` David Sterba
2012-01-18 15:02 ` evergreen
2012-01-24 17:03 ` Hugo Chevrain
2012-01-25 11:30 ` David Sterba
2012-01-18 15:05 ` Markus F.X.J. Oberhumer
2012-01-23 16:19 ` ANN: linux-kernel-lzo-2.06.20120123 - update LZO to v2.06 Markus F.X.J. Oberhumer
2012-01-23 19:12 ` Nitin Gupta
2012-01-25 1:36 ` Andi Kleen
2012-10-09 8:39 ` David Sterba
2012-07-16 18:30 ` ANNOUNCE: linux-kernel-lzo-20120716 - update LZO Markus F.X.J. Oberhumer
2012-07-19 20:58 ` richard -rw- weinberger
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=1326414530-10789-1-git-send-email-andi@firstfloor.org \
--to=andi@firstfloor.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).