mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: liulongfang <liulongfang@huawei.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <wangzhou1@hisilicon.com>, <linux-crypto@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto/hisilicon: Add null judgment to the callback interface
Date: Fri, 30 Sep 2022 11:48:02 +0800	[thread overview]
Message-ID: <717adf23-3080-5041-14ed-6ab5dcaddbf9@huawei.com> (raw)
In-Reply-To: <YzZZTsIHLSkuufeb@gondor.apana.org.au>

On 2022/9/30 10:49, Herbert Xu wrote:
> On Fri, Sep 30, 2022 at 10:43:20AM +0800, Longfang Liu wrote:
>> The algorithm acceleration function interface provided by the
>> current crypto subsystem is in asynchronous mode, but some users
>> will call it in synchronous mode, thus not providing a callback
>> interface for the "base.complete" of the request.
> 
> Please give more details.  Who is calling the callback functions
> in synchronous mode?
> 

Even if the task is sent in synchronous mode, when using the hardware
driver, the hardware still informs the driver software through an
interrupt after completing the task, and the workqueue in the driver
software will call this callback function.

And I found that the device drivers of other manufacturers under the
crypto subsystem are also in this asynchronous mode, and this problem
is also encountered when using the synchronous mode.

> Thanks,
> 
Thanks,
Longfang.

  reply	other threads:[~2022-09-30  3:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30  2:43 Longfang Liu
2022-09-30  2:49 ` Herbert Xu
2022-09-30  3:48   ` liulongfang [this message]
2022-10-28  3:57     ` Herbert Xu
2022-10-29  1:25       ` liulongfang
2022-11-04  9:08         ` Herbert Xu
2022-11-07 13:22           ` liulongfang
2022-11-08  9:59             ` Herbert Xu
2022-11-09  6:21               ` liulongfang
2022-11-09  9:18                 ` Herbert Xu
2022-11-10  2:03                   ` liulongfang
2022-11-10  3:20                     ` Herbert Xu
2022-11-10  4:11                       ` liulongfang
2022-11-10  8:53                         ` Herbert Xu
2022-11-12  1:51                           ` liulongfang
2022-10-28  2:26   ` liulongfang

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=717adf23-3080-5041-14ed-6ab5dcaddbf9@huawei.com \
    --to=liulongfang@huawei.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wangzhou1@hisilicon.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

all inboxes | Powered by JetHome®