[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZdQ0Bfw82Uzsv7cK@gondor.apana.org.au>
Date: Tue, 20 Feb 2024 13:09:25 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Barry Song <21cnbao@...il.com>
Cc: akpm@...ux-foundation.org, davem@...emloft.net, hannes@...xchg.org,
linux-crypto@...r.kernel.org, linux-mm@...ck.org, nphamcs@...il.com,
yosryahmed@...gle.com, zhouchengming@...edance.com,
chriscli@...gle.com, chrisl@...nel.org, ddstreet@...e.org,
linux-kernel@...r.kernel.org, sjenning@...hat.com,
vitaly.wool@...sulko.com, Barry Song <v-songbaohua@...o.com>,
Yang Shen <shenyang39@...wei.com>,
Zhou Wang <wangzhou1@...ilicon.com>,
Tom Zanussi <tom.zanussi@...ux.intel.com>
Subject: Re: [PATCH v4 1/3] crypto: introduce crypto_acomp_get_alg_flags to
expose algorithm flags
On Tue, Feb 20, 2024 at 06:05:16PM +1300, Barry Song wrote:
>
> So it could be something like:
> if data is short, acomp driver works by polling; if data is
> long, acomp driver works by sleeping and waiting.
This sort of logic is specific to each piece of hardware and
should go into the driver.
There is no reason why an async driver cannot return synchronously.
The API fully supports this mode of operation.
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