DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"Ji, Kai" <kai.ji@intel.com>,  "dev@dpdk.org" <dev@dpdk.org>
Cc: "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"g.singh@nxp.com" <g.singh@nxp.com>
Subject: Re: [dpdk-dev] [EXT] [dpdk-dev v1] test/crypto: maxlen calculation update
Date: Thu, 7 Oct 2021 13:59:40 +0000	[thread overview]
Message-ID: <CO6PR18MB4484052CD01F6DCCF95554B3D8B19@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CY4PR11MB1718157B2C93F2F32D8B4173B8B19@CY4PR11MB1718.namprd11.prod.outlook.com>

Hi Fan,

> Hi Akhil and Hemant,
> 
> This is a generic problem to raw_api applies either with dst_buf added or
> not.
> 
> The idea is for SGL test when Wireless algo digest encrypted case is tested
> and
> RTE_MAX(cipher_off + cipher len, auth_off + auth_len) is smaller than
> RTE_MAX(cipher_off + cipher len, auth_off + auth_len + digest_len), the
> original
> code will not add digest data SGL info into rte_crypto_sgl, leave alone the 4-
> byte
> digest is split into 2 2-byte segments.
> 

There are comments in the patch 
/* oop is not supported in raw hw dp api */

This is now supported in the patchset that I mentioned.
So Can we update according to that?


  reply	other threads:[~2021-10-07 13:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29 15:38 [dpdk-dev] " Kai Ji
2021-09-30  9:43 ` [dpdk-dev] FW: " Zhang, Roy Fan
2021-10-07 12:46 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-10-07 13:54   ` Zhang, Roy Fan
2021-10-07 13:59     ` Akhil Goyal [this message]
2021-10-07 14:34       ` Zhang, Roy Fan
2021-10-07 15:20         ` Akhil Goyal
2021-10-07 15:43           ` Zhang, Roy Fan
2021-10-08 11:40           ` Ji, Kai
2021-10-08 11:33 ` [dpdk-dev] [dpdk-dev v2] " Kai Ji
2021-10-31 19:26   ` [dpdk-dev] [EXT] " Akhil Goyal

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=CO6PR18MB4484052CD01F6DCCF95554B3D8B19@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=dev@dpdk.org \
    --cc=g.singh@nxp.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=kai.ji@intel.com \
    --cc=roy.fan.zhang@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).