From: js1304@gmail.com
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel@vger.kernel.org, kernel-team@lge.com,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: [PATCH v4 0/4] zram: implement deduplication in zram
Date: Wed, 26 Apr 2017 09:52:22 +0900 [thread overview]
Message-ID: <1493167946-10936-1-git-send-email-iamjoonsoo.kim@lge.com> (raw)
From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Changes from v3
o fix module build problem
o make zram_dedup_enabled() statically return false if CONFIG_ZRAM_DEDUP=n
Changes from v2
o rebase to latest zram code
o manage alloc/free of the zram_entry in zram_drv.c
o remove useless RB_CLEAR_NODE
o set RO permission tor use_deup sysfs entry if CONFIG_ZRAM_DEDUP=n
Changes from v1
o reogranize dedup specific functions
o support Kconfig on/off
o update zram documents
o compare all the entries with same checksum (patch #4)
This patchset implements deduplication feature in zram. Motivation
is to save memory usage by zram. There are detailed description
about motivation and experimental results on patch #2 so please
refer it.
Thanks.
Joonsoo Kim (4):
zram: introduce zram_entry to prepare dedup functionality
zram: implement deduplication in zram
zram: make deduplication feature optional
zram: compare all the entries with same checksum for deduplication
Documentation/ABI/testing/sysfs-block-zram | 10 ++
Documentation/blockdev/zram.txt | 3 +
drivers/block/zram/Kconfig | 14 ++
drivers/block/zram/Makefile | 3 +-
drivers/block/zram/zram_dedup.c | 254 +++++++++++++++++++++++++++++
drivers/block/zram/zram_dedup.h | 45 +++++
drivers/block/zram/zram_drv.c | 184 +++++++++++++++++----
drivers/block/zram/zram_drv.h | 32 +++-
8 files changed, 507 insertions(+), 38 deletions(-)
create mode 100644 drivers/block/zram/zram_dedup.c
create mode 100644 drivers/block/zram/zram_dedup.h
--
2.7.4
next reply other threads:[~2017-04-26 0:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 0:52 js1304 [this message]
2017-04-26 0:52 ` [PATCH v4 1/4] zram: introduce zram_entry to prepare dedup functionality js1304
2017-04-26 0:52 ` [PATCH v4 2/4] zram: implement deduplication in zram js1304
2017-04-26 2:14 ` Sergey Senozhatsky
2017-04-26 5:57 ` Joonsoo Kim
2017-04-26 6:29 ` Minchan Kim
2017-04-26 6:59 ` Joonsoo Kim
2017-04-26 7:21 ` Sergey Senozhatsky
2017-04-26 7:39 ` Minchan Kim
2017-04-26 7:12 ` Sergey Senozhatsky
2017-04-26 2:37 ` Sergey Senozhatsky
2017-04-26 5:59 ` Joonsoo Kim
2017-04-26 6:04 ` Sergey Senozhatsky
2017-04-26 4:02 ` Sergey Senozhatsky
2017-04-26 6:04 ` Joonsoo Kim
2017-04-26 6:21 ` Sergey Senozhatsky
2017-04-27 6:57 ` Joonsoo Kim
2017-04-27 7:46 ` Sergey Senozhatsky
2017-05-02 5:31 ` Joonsoo Kim
2017-04-26 4:28 ` Sergey Senozhatsky
2017-04-26 6:08 ` Joonsoo Kim
2017-04-26 6:14 ` Sergey Senozhatsky
2017-04-26 0:52 ` [PATCH v4 3/4] zram: make deduplication feature optional js1304
2017-04-26 0:52 ` [PATCH v4 4/4] zram: compare all the entries with same checksum for deduplication js1304
2017-04-27 7:49 ` [PATCH v4 0/4] zram: implement deduplication in zram Sergey Senozhatsky
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=1493167946-10936-1-git-send-email-iamjoonsoo.kim@lge.com \
--to=js1304@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®