From: Herbert Xu <herbert@gondor.apana.org.au>
To: Barry Song <21cnbao@gmail.com>
Cc: akpm@linux-foundation.org, davem@davemloft.net,
hannes@cmpxchg.org, linux-crypto@vger.kernel.org,
linux-mm@kvack.org, nphamcs@gmail.com, yosryahmed@google.com,
zhouchengming@bytedance.com, chriscli@google.com,
chrisl@kernel.org, ddstreet@ieee.org,
linux-kernel@vger.kernel.org, sjenning@redhat.com,
vitaly.wool@konsulko.com, Barry Song <v-songbaohua@oppo.com>,
Yang Shen <shenyang39@huawei.com>,
Zhou Wang <wangzhou1@hisilicon.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: Re: [PATCH v4 1/3] crypto: introduce crypto_acomp_get_alg_flags to expose algorithm flags
Date: Tue, 20 Feb 2024 13:09:25 +0800 [thread overview]
Message-ID: <ZdQ0Bfw82Uzsv7cK@gondor.apana.org.au> (raw)
In-Reply-To: <CAGsJ_4yP1Z4xAy5DEiaPB14YsOSYuYa80C-UY6SC2_eT7vhK9g@mail.gmail.com>
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@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2024-02-20 5:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 2:55 [PATCH v4 0/3] mm/zswap & crypto/compress: remove a couple of memcpy Barry Song
2024-02-20 2:55 ` [PATCH v4 1/3] crypto: introduce crypto_acomp_get_alg_flags to expose algorithm flags Barry Song
2024-02-20 4:13 ` Herbert Xu
2024-02-20 5:05 ` Barry Song
2024-02-20 5:09 ` Herbert Xu [this message]
2024-02-20 5:25 ` Barry Song
2024-02-20 2:55 ` [PATCH v4 2/3] mm/zswap: remove the memcpy if acomp is not sleepable Barry Song
2024-02-20 2:55 ` [PATCH v4 3/3] crypto: scompress: remove memcpy if sg_nents is 1 Barry Song
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZdQ0Bfw82Uzsv7cK@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chriscli@google.com \
--cc=chrisl@kernel.org \
--cc=davem@davemloft.net \
--cc=ddstreet@ieee.org \
--cc=hannes@cmpxchg.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=shenyang39@huawei.com \
--cc=sjenning@redhat.com \
--cc=tom.zanussi@linux.intel.com \
--cc=v-songbaohua@oppo.com \
--cc=vitaly.wool@konsulko.com \
--cc=wangzhou1@hisilicon.com \
--cc=yosryahmed@google.com \
--cc=zhouchengming@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox