linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Joonsoo Kim <js1304@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Minchan Kim <minchan@kernel.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	linux-kernel@vger.kernel.org,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: [PATCH 0/2] prepare zram for crypto api-powered zcomp
Date: Fri, 28 Aug 2015 05:02:12 -0700	[thread overview]
Message-ID: <1440763334-6750-1-git-send-email-sergey.senozhatsky@gmail.com> (raw)
In-Reply-To: <1440052504-15442-8-git-send-email-iamjoonsoo.kim@lge.com>

Hi,

I think those are the changes we need to do in zram. The rest
is zcomp specific. I'll be quite surprised to find out that
we need to change (in zram_drv) more.

Sergey Senozhatsky (2):
  zram: make stream find and release functions static
  zram: pass zstrm down to decompression path

 drivers/block/zram/zcomp.c    | 30 +++++++++++++++++++++++++++---
 drivers/block/zram/zcomp.h    | 11 ++++++++---
 drivers/block/zram/zram_drv.c | 26 +++++++++++++++++++-------
 3 files changed, 54 insertions(+), 13 deletions(-)

-- 
2.5.0.400.gff86faf


  parent reply	other threads:[~2015-08-28 12:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20  6:34 [PATCH v2 0/8] zram: introduce crypto compress noctx API and use it on zram Joonsoo Kim
2015-08-20  6:34 ` [PATCH v2 1/8] crypto: support (de)compression API that doesn't require tfm object Joonsoo Kim
2015-08-20  6:47   ` Herbert Xu
2015-08-20  7:52     ` Joonsoo Kim
2015-08-20  7:50       ` Herbert Xu
2015-08-20  8:05         ` Joonsoo Kim
2015-08-20  6:34 ` [PATCH v2 2/8] crypto/lzo: support decompress_noctx Joonsoo Kim
2015-08-27  1:54   ` Sergey Senozhatsky
2015-08-20  6:34 ` [PATCH v2 3/8] crypyo/lz4: " Joonsoo Kim
2015-08-27  1:56   ` Sergey Senozhatsky
2015-08-20  6:35 ` [PATCH v2 4/8] crypto/lz4hc: " Joonsoo Kim
2015-08-27  1:57   ` Sergey Senozhatsky
2015-08-20  6:35 ` [PATCH v2 5/8] crypto/842: " Joonsoo Kim
2015-08-20  6:35 ` [PATCH v2 6/8] zram: change zcomp_compress interface Joonsoo Kim
2015-08-27  2:14   ` Sergey Senozhatsky
2015-08-20  6:35 ` [PATCH v2 7/8] zram: use crypto API for compression Joonsoo Kim
2015-08-27  4:01   ` Sergey Senozhatsky
2015-08-28 12:02   ` Sergey Senozhatsky [this message]
2015-08-28 12:02     ` [PATCH 1/2] zram: make stream find and release functions static Sergey Senozhatsky
2015-08-28 12:02     ` [PATCH 2/2] zram: pass zstrm down to decompression path Sergey Senozhatsky
2015-09-01  1:22     ` [PATCH 0/2] prepare zram for crypto api-powered zcomp Minchan Kim
2015-09-01  1:41       ` Sergey Senozhatsky
2015-09-01  2:06         ` Minchan Kim
2015-09-01  2:12           ` Sergey Senozhatsky
2015-09-07  5:32             ` Joonsoo Kim
2015-08-20  6:35 ` [PATCH v2 8/8] zram: use decompress_noctx Joonsoo Kim
2015-08-27  4:07   ` Sergey Senozhatsky
2015-08-27  5:47     ` 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=1440763334-6750-1-git-send-email-sergey.senozhatsky@gmail.com \
    --to=sergey.senozhatsky@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=js1304@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=sergey.senozhatsky.work@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).