linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Kai Ye <yekai13@huawei.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	wangzhou1@hisilicon.com
Subject: Re: [PATCH 0/8] crypto: hisilicon - supports to configure function's QoS for ACC
Date: Thu, 17 Jun 2021 16:01:23 +0800	[thread overview]
Message-ID: <20210617080123.GE10662@gondor.apana.org.au> (raw)
In-Reply-To: <1623402410-63906-1-git-send-email-yekai13@huawei.com>

On Fri, Jun 11, 2021 at 05:06:42PM +0800, Kai Ye wrote:
> Based on the Token bucket algorithm. The QM can limit the throughput
> of functions in Kunpeng930. By the device debugfs node that named
> "alg_qos", the ACC driver supports to configue each function's QoS
> in the host. Based on the communication between pf and vf, the driver
> supports reading each function's QoS in the host and VM also by the
> debugfs node.
> 
> Kai Ye (8):
>   crypto: hisilicon/qm - supports writing QoS int the Host
>   crypto: hisilicon/qm - add the "alg_qos" file node
>   crypto: hisilicon/qm - merges the work initialization process into a
>     single function
>   crypto: hisilicon/qm - add pf ping single vf function
>   crypto: hisilicon/qm - supports to inquiry each function's QoS
>   crypto: hisilicon/sec - adds the max shaper type rate
>   crypto: hisilicon/hpre - adds the max shaper type rate
>   crypto: hisilicon/zip - adds the max shaper type rate
> 
>  drivers/crypto/hisilicon/hpre/hpre_main.c |   7 +
>  drivers/crypto/hisilicon/qm.c             | 909 +++++++++++++++++++++++-------
>  drivers/crypto/hisilicon/qm.h             |  14 +
>  drivers/crypto/hisilicon/sec2/sec_main.c  |   7 +
>  drivers/crypto/hisilicon/zip/zip_main.c   |  11 +
>  5 files changed, 757 insertions(+), 191 deletions(-)

All applied.  Thanks.
-- 
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

      parent reply	other threads:[~2021-06-17  8:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11  9:06 [PATCH 0/8] crypto: hisilicon - supports to configure function's QoS for ACC Kai Ye
2021-06-11  9:06 ` [PATCH 1/8] crypto: hisilicon/qm - supports writing QoS int the host Kai Ye
2021-06-11  9:06 ` [PATCH 2/8] crypto: hisilicon/qm - add the "alg_qos" file node Kai Ye
2021-06-11  9:06 ` [PATCH 3/8] crypto: hisilicon/qm - merges the work initialization process into a single function Kai Ye
2021-06-11  9:06 ` [PATCH 4/8] crypto: hisilicon/qm - add pf ping single vf function Kai Ye
2021-06-11  9:06 ` [PATCH 5/8] crypto: hisilicon/qm - supports to inquiry each function's QoS Kai Ye
2021-06-11  9:06 ` [PATCH 6/8] crypto: hisilicon/sec - adds the max shaper type rate Kai Ye
2021-06-11  9:06 ` [PATCH 7/8] crypto: hisilicon/hpre " Kai Ye
2021-06-11  9:06 ` [PATCH 8/8] crypto: hisilicon/zip " Kai Ye
2021-06-17  8:01 ` Herbert Xu [this message]

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=20210617080123.GE10662@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wangzhou1@hisilicon.com \
    --cc=yekai13@huawei.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;
as well as URLs for NNTP newsgroup(s).