[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150921131754.GA8706@swordfish>
Date: Mon, 21 Sep 2015 22:17:54 +0900
From: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc: Joonsoo Kim <js1304@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Minchan Kim <minchan@...nel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
Stephan Mueller <smueller@...onox.de>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH 0/9] use CRYPTO_ALG_TFM_MAY_SHARE cra flag (full
patchset)
On (09/21/15 22:13), Sergey Senozhatsky wrote:
> RFC
>
> resend reason:
> git (2.6.0-rc2) has crashed and spme patches were not sent out.
>
>
> Sorry for the noise.
>
> ===================
what a day... really sorry.
(release 2.5.3) git has crashed again
[Net::SMTP::SSL] Connection closed at /usr/lib/git-core/git-send-email line 1351.
fatal: 'send-email' appears to be a git command, but we were not
able to execute it. Maybe git-send-email is broken?
hm...
-ss
>
> This patch set implements a bit different approach to shared tfm. It
> defines a new CRYPTO_ALG_TFM_MAY_SHARE ->cra_flag which each algorithm
> setups in its `static struct crypto_alg'. Crypto API provides
> crypto_tfm_may_share() function that returns true if the algorithm
> has CRYPTO_ALG_TFM_MAY_SHARE set and, thus, we can supply a shared
> `struct crypto_comp *tfm'.
>
> Not properly tested yet.
>
>
> Sergey Senozhatsky (9):
> crypto: introduce CRYPTO_ALG_TFM_MAY_SHARE flag
> crypto/lzo: set CRYPTO_ALG_TFM_MAY_SHARE
> crypto/lz4: set CRYPTO_ALG_TFM_MAY_SHARE
> crypto/lz4hc: set CRYPTO_ALG_TFM_MAY_SHARE
> crypto/842: set CRYPTO_ALG_TFM_MAY_SHARE
> zram: make stream find and release functions static
> zram: pass zstrm down to decompression path
> zram: use crypto API for compression
> zram: use crypto CRYPTO_ALG_TFM_MAY_SHARE API
>
> crypto/842.c | 3 +-
> crypto/lz4.c | 3 +-
> crypto/lz4hc.c | 3 +-
> crypto/lzo.c | 3 +-
> drivers/block/zram/Kconfig | 8 ++--
> drivers/block/zram/Makefile | 4 +-
> drivers/block/zram/zcomp.c | 103 +++++++++++++++++++++++++++++++----------
> drivers/block/zram/zcomp.h | 42 +++++++----------
> drivers/block/zram/zcomp_lz4.c | 47 -------------------
> drivers/block/zram/zcomp_lz4.h | 17 -------
> drivers/block/zram/zcomp_lzo.c | 47 -------------------
> drivers/block/zram/zcomp_lzo.h | 17 -------
> drivers/block/zram/zram_drv.c | 32 +++++++++----
> include/linux/crypto.h | 10 ++++
> 14 files changed, 138 insertions(+), 201 deletions(-)
> delete mode 100644 drivers/block/zram/zcomp_lz4.c
> delete mode 100644 drivers/block/zram/zcomp_lz4.h
> delete mode 100644 drivers/block/zram/zcomp_lzo.c
> delete mode 100644 drivers/block/zram/zcomp_lzo.h
>
> --
> 2.6.0.rc2.10.gf4d9753
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists