[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160129100901.GA17272@gondor.apana.org.au>
Date: Fri, 29 Jan 2016 18:09:01 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Joonsoo Kim <iamjoonsoo.kim@....com>
Cc: "Li, Weigang" <weigang.li@...el.com>,
"David S. Miller" <davem@...emloft.net>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Minchan Kim <minchan@...nel.org>,
Dan Streetman <ddstreet@...e.org>,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 04/10] crypto/compress: add asynchronous compression
support
On Thu, Jan 28, 2016 at 12:19:42PM +0900, Joonsoo Kim wrote:
>
> I have tested asynchronous compression APIs in zram and I saw
> regression. Atomic allocation and setting up SG lists are culprit
> for this regression. Moreover, zram optimizes linearisation
So which is it, atomic allocations or setting up SG lists? There
is nothing in acomp that requires you to do an atomic allocation.
Cheers,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists