Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp2362815ybk;
        Mon, 11 May 2020 19:56:00 -0700 (PDT)
X-Google-Smtp-Source: APiQypK+SsCm4Z1rn/W6QPxkiDF7oQx1wsawGoTl5ena/o5E1K1fJ+swb3gQmcViwZqXrTsZytPC
X-Received: by 2002:aa7:cd08:: with SMTP id b8mr15611770edw.96.1589252160833;
        Mon, 11 May 2020 19:56:00 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1589252160; cv=none;
        d=google.com; s=arc-20160816;
        b=Jm8dPiptu1OAtpQNtqKVRY5GASfceuVvjNhUx9HiGxR39BGBQHo4ktXaKzm6n0inf2
         3DR0zJcJTipCpm0pDt4Qvi4lMYqvuV3VsCuSmeXEDpppFRKSRpXbChMgpjPs0cFwdJVj
         PThiNqifH5sQSdySB9D3IqrqOQEhsx5xTvtv58CGIM6PS++YXlcViP88N1dmhfrw+3wq
         891OpaAav2xkb1+QhdJDIqEiTGnNZRsNWoqE5YRGwk8vDI8VLUuFbv8Xf1AaHUxZMiMQ
         UBx4V3+8nVqApkkuwdrZ4PsV1M5uUimchIFcRuJb04mKqHYXDRdJlIgHbemiWZI54IRK
         PkAw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-id:precedence:sender:content-transfer-encoding:mime-version
         :user-agent:date:message-id:subject:from:to;
        bh=xvNHe7nW8/R1yBZaKH7CeKaHjriEqZlmGX1U6JpJY0c=;
        b=ythRUjS3zWhaS8Vscd7iMNn8mmHWyc9AprNWxyySHVno8MSiKXPxu0Kptl8L2eOaSY
         5f8UsWeB/u31Tmz9MiSVDAqOsDPSBUvD9BE0qpB+A0tEfo7L+Ugmgcw7cfVihZq1tphn
         BAzEN6lGYiEVobJyzwkN08/gcXFM5E2jVVvgA5znDQXR/4OB3MB0runlf3z0ktFHcNwf
         Tb18XmBO+W1DkDAv93w6WCfBJ2GvDHDzoU7RwSDixFCUoJILc2NE203rtLL4hsyA1zT2
         vJhL7KrNAwKoJRiQkj7adneQfrBhSV//xufLIdncn0DAd1p11/VcWtvC3i37jruF2n2g
         2CKg==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org
Return-Path: <linux-crypto-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18])
        by mx.google.com with ESMTP id ds3si1788543ejc.221.2020.05.11.19.55.26;
        Mon, 11 May 2020 19:56:00 -0700 (PDT)
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;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1727910AbgELCzV (ORCPT <rfc822;zhijun.chen.lk@gmail.com>
        + 99 others); Mon, 11 May 2020 22:55:21 -0400
Received: from szxga06-in.huawei.com ([45.249.212.32]:39652 "EHLO huawei.com"
        rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP
        id S1727892AbgELCzV (ORCPT <rfc822;linux-crypto@vger.kernel.org>);
        Mon, 11 May 2020 22:55:21 -0400
Received: from DGGEMS404-HUB.china.huawei.com (unknown [172.30.72.60])
        by Forcepoint Email with ESMTP id EB667E78D5189A354AC2
        for <linux-crypto@vger.kernel.org>; Tue, 12 May 2020 10:55:19 +0800 (CST)
Received: from [127.0.0.1] (10.67.101.242) by DGGEMS404-HUB.china.huawei.com
 (10.3.19.204) with Microsoft SMTP Server id 14.3.487.0; Tue, 12 May 2020
 10:55:14 +0800
To:     <linux-crypto@vger.kernel.org>
From:   Xu Zaibo <xuzaibo@huawei.com>
Subject: Question: SHASH or AHASH.
Message-ID: <7eedd7ca-18a3-f5de-e477-f4b468cfc7f1@huawei.com>
Date:   Tue, 12 May 2020 10:55:13 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.7.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.67.101.242]
X-CFilter-Loop: Reflected
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-crypto.vger.kernel.org>
X-Mailing-List: linux-crypto@vger.kernel.org

Hi,

Sorry for disturbing you.
I got a question: which API should my I/O Crypto device driver use, 
SHASH or AHASH?
For performance, I would like to use AHASH since I/O device doing better 
at asynchronous mode.

Thanks,

Zaibo

.