Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1232578 > unrolled thread

Re: [PATCH v3 9/9] zram: use crypto decompress_noctx API

Started byJoonsoo Kim <iamjoonsoo.kim@lge.com>
First post2015-09-25 07:50 +0200
Last post2015-09-25 07:50 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v3 9/9] zram: use crypto decompress_noctx API Joonsoo Kim <iamjoonsoo.kim@lge.com> - 2015-09-25 07:50 +0200

#1232578 — Re: [PATCH v3 9/9] zram: use crypto decompress_noctx API

FromJoonsoo Kim <iamjoonsoo.kim@lge.com>
Date2015-09-25 07:50 +0200
SubjectRe: [PATCH v3 9/9] zram: use crypto decompress_noctx API
Message-ID<qcu3o-MY-17@gated-at.bofh.it>
On Mon, Sep 21, 2015 at 04:56:00PM +0900, Sergey Senozhatsky wrote:
> On (09/18/15 14:19), Joonsoo Kim wrote:
> [..]
> > +	/*
> > +	 * Prepare to use crypto decompress_noctx API. One tfm is required
> > +	 * to initialize crypto algorithm properly and fetch corresponding
> > +	 * function pointer. But, it is sharable for multiple concurrent
> > +	 * decompress users.
> > +	 */
> 
> if comp algorithm require zstrm for both compression and decompression,
> then there seems to be no need in allocating sharable ->tfm_noctx, we
> will never use it.
> 

Yes, in that case, NULL will be returned. I should describe it on
somewhere.

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/

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web