DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Kevin O'Sullivan <kevin.osullivan@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "kai.ji@intel.com" <kai.ji@intel.com>
Subject: RE: [EXT] [PATCH v4 0/2] crypto/qat: add cipher-crc offload feature
Date: Wed, 24 May 2023 10:04:15 +0000	[thread overview]
Message-ID: <CO6PR18MB44849BA8906C56150E992136D8419@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230418133942.2088671-1-kevin.osullivan@intel.com>

> This patchset adds support to the QAT PMD for combined cipher-crc
> processing for DOCSIS on the QAT device. The current QAT PMD
> implementation of cipher-crc calculates CRC in software and uses QAT
> for encryption/decryption offload.
> 
> Note: The previous code-path is still retained for QAT firmware
> versions without support for combined cipher-crc offload.
> 
> - Support has been added to DPDK QAT PMD to enable the use of the
> cipher-crc offload feature on gen2/gen3/gen4 QAT devices.
> 
> - A cipher-crc offload capability check has been added to the queue
> pair setup function to determine if the feature is supported on the
> QAT device.
> 
> v1:
> * initial version
> 
> v2:
> * fixed centos compilation error for missing braces around
>   initializer
> 
> v3:
> * updated the file qat.rst with details of new configuration
> 
> v4:
> * updated v23.07 release note
> * moved cipher crc capability check test vectors to top of
>   qat_qp.c and made the vectors static const
> * changed log string to be all on one line in qat_device.c
> * changed word parameter to devargs in qat.rst
Series applied to dpdk-next-crypto

Updated cipher-crc -> Cipher-CRC in patch title and description


      parent reply	other threads:[~2023-05-24 10:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 12:12 [PATCH 0/2] crypto/qat: added " Kevin O'Sullivan
2023-03-08 12:12 ` [PATCH 1/2] crypto/qat: added cipher-crc offload support Kevin O'Sullivan
2023-03-08 12:12 ` [PATCH 2/2] crypto/qat: added cipher-crc cap check Kevin O'Sullivan
2023-03-09 14:33 ` [PATCH v2 0/2] crypto/qat: add cipher-crc offload feature Kevin O'Sullivan
2023-03-09 14:33   ` [PATCH v2 1/2] crypto/qat: add cipher-crc offload support to fw interface Kevin O'Sullivan
2023-03-09 14:33   ` [PATCH v2 2/2] crypto/qat: add cipher-crc offload support Kevin O'Sullivan
2023-03-13 14:26   ` [PATCH v3 0/2] crypto/qat: add cipher-crc offload feature Kevin O'Sullivan
2023-03-13 14:26     ` [PATCH v3 1/2] crypto/qat: add cipher-crc offload support to fw interface Kevin O'Sullivan
2023-03-16 12:24       ` Ji, Kai
2023-03-13 14:26     ` [PATCH v3 2/2] crypto/qat: add cipher-crc offload support Kevin O'Sullivan
2023-03-16 12:25       ` Ji, Kai
2023-03-16 19:15       ` [EXT] " Akhil Goyal
2023-03-20 16:28         ` O'Sullivan, Kevin
2023-04-18 13:39     ` [PATCH v4 0/2] crypto/qat: add cipher-crc offload feature Kevin O'Sullivan
2023-04-18 13:39       ` [PATCH v4 1/2] crypto/qat: add cipher-crc offload support to fw interface Kevin O'Sullivan
2023-04-18 13:39       ` [PATCH v4 2/2] crypto/qat: support cipher-crc offload Kevin O'Sullivan
2023-05-24 10:04       ` Akhil Goyal [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=CO6PR18MB44849BA8906C56150E992136D8419@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.com \
    --cc=kevin.osullivan@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;
as well as URLs for NNTP newsgroup(s).