Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752122AbbHMHgs (ORCPT ); Thu, 13 Aug 2015 03:36:48 -0400 Received: from LGEMRELSE7Q.lge.com ([156.147.1.151]:42923 "EHLO lgemrelse7q.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751998AbbHMHgq (ORCPT ); Thu, 13 Aug 2015 03:36:46 -0400 X-Original-SENDERIP: 10.177.222.220 X-Original-MAILFROM: iamjoonsoo.kim@lge.com Date: Thu, 13 Aug 2015 16:42:27 +0900 From: Joonsoo Kim To: Herbert Xu Cc: Sergey Senozhatsky , Andrew Morton , Minchan Kim , Nitin Gupta , linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, "David S. Miller" , Stephan Mueller Subject: Re: [PATCH 2/2] zram: use crypto API to compress the page Message-ID: <20150813074227.GA14553@js1304-P5Q-DELUXE> References: <1439432654-23322-1-git-send-email-iamjoonsoo.kim@lge.com> <1439432654-23322-2-git-send-email-iamjoonsoo.kim@lge.com> <20150813035113.GB17958@swordfish> <20150813071941.GB13352@js1304-P5Q-DELUXE> <20150813073233.GA21492@gondor.apana.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150813073233.GA21492@gondor.apana.org.au> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 753 Lines: 19 On Thu, Aug 13, 2015 at 03:32:33PM +0800, Herbert Xu wrote: > On Thu, Aug 13, 2015 at 04:19:41PM +0900, Joonsoo Kim wrote: > > > > If that optimization is really needed for the case that doesn't need > > tfm except fetching function pointer, we can implement sharable tfm > > in crypto subsystem. > > I'm happy to consider changes to the crypto compression interface > as long as it continues to support the existing algorithms and users. Happy to hear that. I will think how it can be improved. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/