[PATCHv6 0/6] add compressing abstraction and multi stream support
From: Sergey Senozhatsky
Date: Fri Feb 21 2014 - 06:54:25 EST
This patchset introduces zcomp compression backend abstraction
adding ability to support compression algorithms other than LZO;
support for multi compression streams, making parallel compressions
possible.
v5->v6 (reviewed by Minchan Kim):
-- handle single compression stream case separately, using mutex locking,
to address perfomance regression
-- handle multi compression stream using spin lock and wait_event()/wake_up()
-- make multi compression stream support configurable (ZRAM_MULTI_STREAM
config option)
v4->v5 (reviewed by Minchan Kim):
-- renamed zcomp buffer_lock; removed src len and dst len from
compress() and decompress(); not using term `buffer' and
`workmem' in code and documentation; define compress() and
decompress() functions for LZO backend; not using goto's;
do not put idle zcomp_strm to idle list tail.
v3->v4:
-- renamed compression backend and working memory structs as requested
by Minchan Kim; fixed several issues noted by Minchan Kim.
Sergey Senozhatsky (6):
zram: introduce compressing backend abstraction
zram: use zcomp compressing backends
zram: factor out single stream compression
zram: add multi stream functionality
zram: enalbe multi stream compression support in zram
zram: document max_comp_streams
Documentation/ABI/testing/sysfs-block-zram | 9 +-
Documentation/blockdev/zram.txt | 24 ++-
drivers/block/zram/Kconfig | 10 ++
drivers/block/zram/Makefile | 2 +-
drivers/block/zram/zcomp.c | 271 +++++++++++++++++++++++++++++
drivers/block/zram/zcomp.h | 56 ++++++
drivers/block/zram/zcomp_lzo.c | 48 +++++
drivers/block/zram/zram_drv.c | 103 +++++++----
drivers/block/zram/zram_drv.h | 10 +-
9 files changed, 486 insertions(+), 47 deletions(-)
create mode 100644 drivers/block/zram/zcomp.c
create mode 100644 drivers/block/zram/zcomp.h
create mode 100644 drivers/block/zram/zcomp_lzo.c
--
1.9.0.291.g027825b
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/