| decompression
zbewalgo |1.30 | 203.30 MBit/s | 530.87 MBit/s
deflate |1.02 | 37.06 MBit/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 |
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
>
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 the
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
,
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
33.07 484.09
deflate_3 1.0533.11 463.57
deflate_1 1.0533.19 469.71
zstd_22 1.06 8.89 647.75
zstd_21 1.0610.70 700.11
zstd_20 1.0610.80 723.42
zstd_19 1.06 12.41 764.24
zbewalgo* 1.51 146.45 581.43
zbewalgo 1.51 146.45
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
s read in blocks of 8 Bytes. These Blocks
are added to an avl-tree. 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
12.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 Warnke (5):
add compressi
s read in blocks of 8 Bytes. These Blocks
are added to an avl-tree. 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
,
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
1.0531.94 481.37
deflate_2 1.0533.07 484.09
deflate_3 1.0533.11 463.57
deflate_1 1.0533.19 469.71
zstd_22 1.06 8.89 647.75
zstd_21 1.0610.70 700.11
zstd_20 1.0610.80 723.42
zstd_19 1.06 12.41 764.24
zbewal
s read in blocks of 8 Bytes. These Blocks
are added to an avl-tree. 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
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
,
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
Hi Philippe,
> Am 20.03.2018 um 17:30 schrieb Philippe Ombredanne :
>
> 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 - Currently it is not publish
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
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
,
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
69.71
zstd_22 1.06 8.89 647.75
zstd_21 1.0610.70 700.11
zstd_20 1.0610.80 723.42
zstd_19 1.06 12.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>
---
--
2.14.1
s read in blocks of 8 Bytes. These Blocks
are added to an avl-tree. 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
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
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
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 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
| compression| decompression
zbewalgo |1.30 | 203.30 MBit/s | 530.87 MBit/s
deflate |1.02 | 37.06 MBit/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.3
30 matches
Mail list logo
