Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH 2/5] crypto:hisilicon/sec2 - update busy processing logic
To:     Herbert Xu <herbert@gondor.apana.org.au>
CC:     <linux-crypto@vger.kernel.org>
References: <1593167529-22463-1-git-send-email-liulongfang@huawei.com>
 <1593167529-22463-3-git-send-email-liulongfang@huawei.com>
 <20200703041440.GA7858@gondor.apana.org.au>
From:   liulongfang <liulongfang@huawei.com>
Message-ID: <9a1eff92-537b-60e3-c840-206915d69019@huawei.com>
Date:   Fri, 3 Jul 2020 16:18:54 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <20200703041440.GA7858@gondor.apana.org.au>
Content-Type: text/plain; charset="gbk"
Content-Transfer-Encoding: 7bit
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

On 2020/7/3 12:14, Herbert Xu Wrote:
> On Fri, Jun 26, 2020 at 06:32:06PM +0800, Longfang Liu wrote:
>> From: Kai Ye <yekai13@huawei.com>
>>
>> As before, if a SEC queue is at the 'fake busy' status,
>> the request with a 'fake busy' flag will be sent into hardware
>> and the sending function returns busy. After the request is
>> finished, SEC driver's call back will identify the 'fake busy' flag,
>> and notifies the user that hardware is not busy now by calling
>> user's call back function.
>>
>> Now, a request sent into busy hardware will be cached in the
>> SEC queue's backlog, return '-EBUSY' to user.
>> After the request being finished, the cached requests will
>> be processed in the call back function. to notify the
>> corresponding user that SEC queue can process more requests.
>>
>> Signed-off-by: Kai Ye <yekai13@huawei.com>
>> Reviewed-by: Longfang Liu <liulongfang@huawei.com>
> Why does this driver not take MAY_BACKLOG into account?
>
> Cheers,

OK, I will apply MAY_BACKLOG in the next version soon.

thanks,

Longfang

.