From: Andrew Morton <akpm@linux-foundation.org>
To: js1304@gmail.com
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: Re: [PATCH v2 0/4] zram: implement deduplication in zram
Date: Thu, 30 Mar 2017 15:25:02 -0700 [thread overview]
Message-ID: <20170330152502.c0fd67c4df30db552abce000@linux-foundation.org> (raw)
In-Reply-To: <1490852289-11913-1-git-send-email-iamjoonsoo.kim@lge.com>
On Thu, 30 Mar 2017 14:38:05 +0900 js1304@gmail.com wrote:
> 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.
I'm getting a lot of rejects against the current -mm tree. So this is
one of those patchsets which should be prepared against -mm, please.
I'll be attempting to release another mmotm in the next couple of hours.
next prev parent reply other threads:[~2017-03-30 22:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 5:38 [PATCH v2 0/4] zram: implement deduplication in zram js1304
2017-03-30 5:38 ` [PATCH v2 1/4] zram: introduce zram_entry to prepare dedup functionality js1304
2017-03-30 5:38 ` [PATCH v2 2/4] zram: implement deduplication in zram js1304
2017-04-17 1:38 ` Minchan Kim
2017-04-17 2:22 ` Joonsoo Kim
2017-03-30 5:38 ` [PATCH v2 3/4] zram: make deduplication feature optional js1304
2017-03-30 5:38 ` [PATCH v2 4/4] zram: compare all the entries with same checksum for deduplication js1304
2017-03-30 22:25 ` Andrew Morton [this message]
2017-03-30 23:40 ` [PATCH v2 0/4] zram: implement deduplication in zram Minchan Kim
2017-04-07 2:00 ` Joonsoo Kim
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=20170330152502.c0fd67c4df30db552abce000@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.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;
as well as URLs for NNTP newsgroup(s).