From: Ahsan Atta <ahsan.atta@intel.com>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, qat-linux@intel.com,
Ahsan Atta <ahsan.atta@intel.com>
Subject: [PATCH RESEND 0/2] crypto: qat - enable three-service mode for QAT GEN5
Date: Fri, 23 Oct 2026 15:48:33 +0100 [thread overview]
Message-ID: <20261023144835.170453-1-ahsan.atta@intel.com> (raw)
Resending and we can ignore the feedback from Sashiko review because we
do not have QAT GEN5 SKUs that have some of the AEs fused off.
QAT GEN5 devices (qat_420xx) have enough accelerator engines to run
three services concurrently, but the driver currently only allows a
maximum of two to be configured at a time, matching the GEN4 limit.
This series lifts that restriction so that symmetric crypto, asymmetric
crypto and compression can be enabled together on GEN5, as is already
possible on GEN6 (qat_6xxx).
In summary:
Patch #1: Define the firmware object layout, ring-to-service mapping,
thread-to-arbiter mapping and service-to-accelerator-engine accounting
required for the sym;asym;dc configuration on GEN5, and register the
new service combination in adf_cfg_services so that it can be selected
through the cfg_services sysfs attribute.
Patch #2: Update the cfg_services ABI documentation to state that GEN5
devices (qat_420xx) support a maximum of three combined services,
alongside the existing GEN6 entry. Documentation only, no functional
change.
Bairavi Alagappan (2):
crypto: qat - enable three-service mode for QAT GEN5 devices
Documentation: qat: document three-service mode for QAT GEN5 devices
Documentation/ABI/testing/sysfs-driver-qat | 4 +-
.../intel/qat/qat_420xx/adf_420xx_hw_data.c | 104 +++++++++++++++++-
.../intel/qat/qat_420xx/adf_420xx_hw_data.h | 6 +
.../intel/qat/qat_common/adf_cfg_services.c | 3 +
.../intel/qat/qat_common/adf_cfg_services.h | 1 +
5 files changed, 113 insertions(+), 5 deletions(-)
base-commit: 9c5d66e1ea78912b8a43ce16a1c14db1357e0ae0
--
2.50.1
next reply other threads:[~2026-10-23 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 14:48 Ahsan Atta [this message]
2026-10-23 14:48 ` [PATCH RESEND 1/2] crypto: qat - enable three-service mode for QAT GEN5 devices Ahsan Atta
2026-10-23 15:03 ` sashiko-bot
2026-10-23 16:32 ` Ahsan Atta
2026-10-23 14:48 ` [PATCH RESEND 2/2] Documentation: qat: document " Ahsan Atta
2026-10-23 15:02 ` sashiko-bot
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=20261023144835.170453-1-ahsan.atta@intel.com \
--to=ahsan.atta@intel.com \
--cc=herbert@gondor.apana.org.au \
--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