DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "declan.doherty@intel.com" <declan.doherty@intel.com>,
	"anoobj@marvell.com" <anoobj@marvell.com>,
	"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
	Manish Tomar <manish.tomar@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v3] app/test-crypto-perf: support PDCP
Date: Mon, 18 Nov 2019 09:38:39 +0000	[thread overview]
Message-ID: <VE1PR04MB6639A24F748D5B9BE7233260E64D0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20191108104610.7474-1-akhil.goyal@nxp.com>

> 
> test-crypto-perf app is updated to calculate PDCP
> throughput numbers.
> 
> 2 new params are added for PDCP
> --pdcp-sn-sz <5/7/12/15/18>
> --pdcp-domain <control/user>
> 
> ./dpdk-test-crypto-perf --master-lcore 0 -l 0,1 --log-level=8 --
> --devtype crypto_dpaa2_sec --optype pdcp --cipher-algo aes-ctr
> --cipher-op encrypt --auth-algo null --auth-op generate  --auth-key-sz
> 16 --ptest throughput --total-ops 100000 --burst-sz 64 --buffer-sz
> 64,390,1512  --pool-sz 4096 --silent --pdcp-sn-sz 12 --pdcp-domain
> control
> 
> Signed-off-by: Manish Tomar <manish.tomar@nxp.com>
> Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com>
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
> changes in v3:
> - fix compilation when rte_security disabled.
> changes in v2:
> -fixed checkpatch warning.

Applied to dpdk-next-crypto



      reply	other threads:[~2019-11-18  9:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 10:46 Akhil Goyal
2019-11-18  9:38 ` 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=VE1PR04MB6639A24F748D5B9BE7233260E64D0@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=manish.tomar@nxp.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).