Received-SPF: pass (google.com: domain of linux-crypto+bounces-4647-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Mon, 3 Jun 2024 11:34:47 +0900
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH 1/3] crypto: scomp - Add setparam interface
Message-ID: <20240603023447.GI8400@google.com>
References: <cover.1716202860.git.herbert@gondor.apana.org.au>
 <84523e14722d0629b2ee9c8e7e3c04aa223c5fb5.1716202860.git.herbert@gondor.apana.org.au>
 <20240531054759.GE8400@google.com>
 <20240531063444.GG8400@google.com>
 <ZlmKX4dD1EcstVmN@gondor.apana.org.au>
 <20240601002415.GH8400@google.com>
 <ZlqbcKUTa5e3rOtH@gondor.apana.org.au>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ZlqbcKUTa5e3rOtH@gondor.apana.org.au>

On (24/06/01 11:54), Herbert Xu wrote:
> On Sat, Jun 01, 2024 at 09:24:15AM +0900, Sergey Senozhatsky wrote:
> >
> > Is it possible to share a tfm? I thought that tfm-s carry some state
> > (compression workmem/scratch buffer) so one cannot do parallel compressions
> > on different CPUs using the same tfm.
> 
> Yes the tfm can be shared.  The data state is kept in the request
> object.

Oh, nice, thanks.

I'll try that new API (and tfm sharing) in zram, coordinate with
android folks on this and will come back to you.