From: Herbert Xu <herbert@gondor.apana.org.au>
To: Damian Muszynski <damian.muszynski@intel.com>
Cc: linux-crypto@vger.kernel.org, qat-linux@intel.com,
Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Subject: Re: [PATCH] crypto: qat - generate dynamically arbiter mappings
Date: Fri, 29 Dec 2023 11:29:50 +0800 [thread overview]
Message-ID: <ZY49LhGOGYK1Wi4P@gondor.apana.org.au> (raw)
In-Reply-To: <20231222131804.8765-1-damian.muszynski@intel.com>
On Fri, Dec 22, 2023 at 02:15:35PM +0100, Damian Muszynski wrote:
> The thread-to-arbiter mapping describes which arbiter can assign jobs
> to an acceleration engine thread.
> The existing mappings are functionally correct, but hardcoded and not
> optimized.
>
> Replace the static mappings with an algorithm that generates optimal
> mappings, based on the loaded configuration.
>
> The logic has been made common so that it can be shared between all
> QAT GEN4 devices.
>
> Signed-off-by: Damian Muszynski <damian.muszynski@intel.com>
> Reviewed-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
> ---
> .../intel/qat/qat_420xx/adf_420xx_hw_data.c | 131 +++++++-----------
> .../intel/qat/qat_4xxx/adf_4xxx_hw_data.c | 110 ++++++++++-----
> .../intel/qat/qat_common/adf_accel_devices.h | 4 +
> .../intel/qat/qat_common/adf_gen4_hw_data.c | 90 ++++++++++++
> .../intel/qat/qat_common/adf_gen4_hw_data.h | 12 ++
> 5 files changed, 235 insertions(+), 112 deletions(-)
Patch 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
prev parent reply other threads:[~2023-12-29 3:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 13:15 [PATCH] crypto: qat - generate dynamically arbiter mappings Damian Muszynski
2023-12-29 3:29 ` 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=ZY49LhGOGYK1Wi4P@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=damian.muszynski@intel.com \
--cc=giovanni.cabiddu@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=qat-linux@intel.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