lgo algorithm.
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto/Kconfig | 8 +
crypto/Makefile | 1 +
crypto/zbewalgo.c| 207 +
include/linux/zbewalgo.h | 59 ++
li
Hi Stephan,
thanks for your fast response.
> Please run checkpatch.pl on the patch and fix the formatting issues.
I've run checkpatch.pl again and fixed all errors and warnings except the
warnings about printk.
Compression does not have it's own subsystem, that is why I used
printk(KERN_INFO
Hi Eric,
>> Currently ZRAM uses the compression-algorithms from the crypto-api.
>> None of the current compression-algorithms in the crypto-api is designed
>> to compress 4KiB chunks of data efficiently.
>> This patch adds a new compression-algorithm especially designed for ZRAM,
>> to compress
Hi Stephan,
>>> In general: I do not think that having larger C functions in header files
>>> is a proper coding style.
>>
>> How should I solve this?
>>
>> Option 1:
>> Move everything in the lib/zbewalgo folder into a single source file.
>> This way there is no function defined in a header
-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto/Kconfig| 8 +
crypto/Makefile | 1 +
crypto/zbewalgo.c | 208
include/linux/zbewalgo.h | 59 +
lib/Kconfig | 3 +
lib/Makefile | 1 +
lib/zb
Hi,
I am working on a new Version for this patch addressing all comments, and
following all guidelines.
Best Regards,
Benjamin Warnke
t/s | 1131.88 MBit/s
lzo |1.00 | 1741.46 MBit/s | 2012.78 MBit/s
lz4 |1.00 | 1458.08 MBit/s | 2013.88 MBit/s
lz4hc |1.00 | 173.19 MBit/s | 2012.37 MBit/s
842 |1.00 | 64.10 MBit/s | 2013.64 MBit/s
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamb
t/s | 2012.78 MBit/s
lz4 |1.00 | 1458.08 MBit/s | 2013.88 MBit/s
lz4hc |1.00 | 173.19 MBit/s | 2012.37 MBit/s
842 |1.00 | 64.10 MBit/s | 2013.64 MBit/s
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
Changes since v2:
- added linux-kernel Ma
Hi Eric,
On 06.03.2018 at 23:13, Eric Biggers wrote:
>
> Hi Benjamin,
>
> On Tue, Mar 06, 2018 at 09:23:08PM +0100, Benjamin Warnke wrote:
>> Currently ZRAM uses compression-algorithms from the crypto-api. ZRAM
>> compresses each page individually. As a result t
Hello,
On(07/03/2018 03:12),Sergey Senozhatsky wrote:
>
> Hello,
>
> On (03/06/18 20:59), Benjamin Warnke wrote:
>> Currently ZRAM uses compression-algorithms from the crypto-api. ZRAM
>> compresses each page individually. As a result the compression algorithm
&g
ed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
Benjamin Warnke (5):
add compression algorithm zBeWalgo
crypto: add zBeWalgo to crypto-api
crypto: add unsafe decompression to api
crypto: configurable compression level
crypto: add flag for unstable encoding
The data-format of zBeWalgo, and some other algorithms is unstable. To
identify such unstable algorithms this patch adds a new flag to the
crypto-api.
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto/zbewalgo.c | 2 +-
include/linux/crypto.h | 6 ++
2
. The avl-tree is mapped directly to an
array. The encoding is a variation of Run Length Encoding using the
indices in the avl-tree as data. The reason for using the tree
with indices is, that the indices can be encoded in less then
8 Bytes each.
Signed-off-by: Benjamin Warnke <4b
Most compression algorithms published by the crypto api are supporting
multiple different compression levels. The crypto api currently just
calls these algorithms with their default compression level.
This patch enables the caller to specify the compression level.
Signed-off-by: Benjamin Warnke
,
which is a bit faster, but does no error checking. These unsafe decompressors
can be applied when the datasource and the whole datapath is trusted.
This patch publishes these existing functions in the crypto-api
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto
This patch adds zBeWalgo to the crypto api so that zBeWalgo can be used by
zram.
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto/Kconfig | 12
crypto/Makefile| 1 +
crypto/testmgr.c | 10 +++
crypto/tes
Most compression algorithms published by the crypto api are supporting
multiple different compression levels. The crypto api currently just
calls these algorithms with their default compression level.
This patch enables the caller to specify the compression level.
Signed-off-by: Benjamin Warnke
1.0610.80 723.42
zstd_19 1.0612.41 764.24
zbewalgo* 1.51 146.45 581.43
zbewalgo 1.51 146.45 592.86
zbewalgo'*1.5438.14 120.96
zbewalgo' 1.5438.14 125.81
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
Benjamin Warnk
. The avl-tree is mapped directly to an
array. The encoding is a variation of Run Length Encoding using the
indices in the avl-tree as data. The reason for using the tree
with indices is, that the indices can be encoded in less then
8 Bytes each.
Signed-off-by: Benjamin Warnke <4b
,
which is a bit faster, but does no error checking. These unsafe decompressors
can be applied when the datasource and the whole datapath is trusted.
This patch publishes these existing functions in the crypto-api
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto
The data-format of zBeWalgo, and some other algorithms is unstable. To
identify such unstable algorithms this patch adds a new flag to the
crypto-api.
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto/zbewalgo.c | 2 +-
include/linux/crypto.h | 6 ++
2
This patch adds zBeWalgo to the crypto api so that zBeWalgo can be used by
zram.
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto/Kconfig| 12
crypto/Makefile | 1 +
crypto/testmgr.c | 10 +++
crypto/tes
This patch adds zBeWalgo to the crypto api so that zBeWalgo can be used by
zram.
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto/Kconfig| 12 +++
crypto/Makefile | 1 +
crypto/testmgr.c | 10 +++
crypto/tes
. The avl-tree is mapped directly to an
array. The encoding is a variation of Run Length Encoding using the
indices in the avl-tree as data. The reason for using the tree
with indices is, that the indices can be encoded in less then
8 Bytes each.
Signed-off-by: Benjamin Warnke <4b
std_21 1.0610.70 700.11
zstd_20 1.0610.80 723.42
zstd_19 1.0612.41 764.24
zbewalgo* 1.51 146.45 581.43
zbewalgo 1.51 146.45 592.86
zbewalgo'*1.5438.14 120.96
zbewalgo' 1.5438.14 125.81
Signed-off-by: Benjamin Warnke
,
which is a bit faster, but does no error checking. These unsafe decompressors
can be applied when the datasource and the whole datapath is trusted.
This patch publishes these existing functions in the crypto-api
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto
Most compression algorithms published by the crypto api are supporting
multiple different compression levels. The crypto api currently just
calls these algorithms with their default compression level.
This patch enables the caller to specify the compression level.
Signed-off-by: Benjamin Warnke
The data-format of zBeWalgo, and some other algorithms is unstable. To
identify such unstable algorithms this patch adds a new flag to the
crypto-api.
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto/zbewalgo.c | 2 +-
include/linux/crypto.h | 6 ++
2
Hi Philippe,
> Am 20.03.2018 um 17:30 schrieb Philippe Ombredanne <pombreda...@nexb.com>:
>
> Hi Benjamin,
>
> On Tue, Mar 20, 2018 at 7:04 AM, Benjamin Warnke
> <4bwar...@informatik.uni-hamburg.de> wrote:
>> zBeWalgo is a completely new algorithm - Curren
. The avl-tree is mapped directly to an
array. The encoding is a variation of Run Length Encoding using the
indices in the avl-tree as data. The reason for using the tree
with indices is, that the indices can be encoded in less then
8 Bytes each.
Signed-off-by: Benjamin Warnke <4b
The data-format of zBeWalgo, and some other algorithms is unstable. To
identify such unstable algorithms this patch adds a new flag to the
crypto-api.
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto/zbewalgo.c | 2 +-
include/linux/crypto.h | 6 ++
2
146.45 581.43
zbewalgo 1.51 146.45 592.86
zbewalgo'*1.5438.14 120.96
zbewalgo' 1.5438.14 125.81
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
--
2.14.1
Most compression algorithms published by the crypto api are supporting
multiple different compression levels. The crypto api currently just
calls these algorithms with their default compression level.
This patch enables the caller to specify the compression level.
Signed-off-by: Benjamin Warnke
,
which is a bit faster, but does no error checking. These unsafe decompressors
can be applied when the datasource and the whole datapath is trusted.
This patch publishes these existing functions in the crypto-api
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto
This patch adds zBeWalgo to the crypto api so that zBeWalgo can be used by
zram.
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto/Kconfig| 12
crypto/Makefile | 1 +
crypto/testmgr.c | 10 +++
crypto/tes
uld mean GPL-2.0+ (e.g. or any
> later version) and this would not match your top level license tag.
Thanks, I have done this correctly in my files, but accidentally written it
wrong in my mail.
Cordinally
Benjamin Warnke
36 matches
Mail list logo