DPDK usage discussions
 help / color / mirror / Atom feed
From: "DAS, SANJIB" <sanjib.das@hpe.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
	"users@dpdk.org" <users@dpdk.org>,  "dts@dpdk.org" <dts@dpdk.org>,
	"test-report@dpdk.org" <test-report@dpdk.org>
Cc: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"DAS, SANJIB" <sanjib.das@hpe.com>
Subject: Re: [dpdk-users] Query on ipsec-secgw with crypto algorithm CCM
Date: Wed, 16 May 2018 07:35:26 +0000	[thread overview]
Message-ID: <TU4PR8401MB06550B48129357A57B580A918D920@TU4PR8401MB0655.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B4358947DD1D@IRSMSX103.ger.corp.intel.com>

Hi Fiona,

One query with dpsk-17.11.2 ipsec-secgw.

I do see API ixgbe_crypto_enable_ipsec() returning me error for both rx/tx (dev_conf.rxmode.offloads/dev_conf.txmode.offloads) offload on my target X86 system.

It fails to read value whatever it writes either on IXGBE_SECRXCTRL or IXGBE_SECTXCTRL.
I am currently debugging this issue, but if I ignore these errors it continues & I can see
its handling packets also.

Does ignoring these errors mean simply its not enabling hw offloads for both rx/tx? 
Is my understanding correct? Other than that does it have any other side effect? 


Thanks,
Sanjib


-----Original Message-----
From: DAS, SANJIB 
Sent: Wednesday, May 9, 2018 5:48 PM
To: 'Trahe, Fiona' <fiona.trahe@intel.com>; users@dpdk.org; dts@dpdk.org; test-report@dpdk.org
Cc: Zhang, Roy Fan <roy.fan.zhang@intel.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
Subject: RE: Query on ipsec-secgw with crypto algorithm CCM

Thanks a lot Fiona. It worked.

Thanks,
Sanjib

my page-0 wiki



-----Original Message-----
From: Trahe, Fiona [mailto:fiona.trahe@intel.com]
Sent: Wednesday, May 9, 2018 5:22 PM
To: DAS, SANJIB <sanjib.das@hpe.com>; users@dpdk.org; dts@dpdk.org; test-report@dpdk.org
Cc: Zhang, Roy Fan <roy.fan.zhang@intel.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>
Subject: RE: Query on ipsec-secgw with crypto algorithm CCM

CCM aead-iv-size should be between 7 and 13, you're setting to 16.
See drivers/crypto/openssl/rte_openssl_pmd_ops.c for openssl capabilities


> -----Original Message-----
> From: DAS, SANJIB [mailto:sanjib.das@hpe.com]
> Sent: Wednesday, May 9, 2018 4:19 AM
> To: Trahe, Fiona <fiona.trahe@intel.com>; users@dpdk.org; 
> dts@dpdk.org; test-report@dpdk.org
> Cc: Zhang, Roy Fan <roy.fan.zhang@intel.com>; De Lara Guarch, Pablo 
> <pablo.de.lara.guarch@intel.com>; DAS, SANJIB <sanjib.das@hpe.com>
> Subject: RE: Query on ipsec-secgw with crypto algorithm CCM
> 
> Thanks Fiona,
> 
> Recently I was trying with "dpdk-test-crypto-perf"  application & PMD as openssl.
> But I do see it fails for CCM (dpdk-17.11.2). This API fails 
> rte_cryptodev_sym_capability_check_aead(). It all works fine with GCM.
> 
> 
> I used this command
> 
> ./dpdk-test-crypto-perf -l 1-2 --vdev crypto_openssl -w 0000:00:00.0
> -- --devtype crypto_openssl --aead- algo aes-ccm --aead-key-sz 16 
> --aead-iv-sz 16 --aead-op encrypt --aead-aad-sz 16 --digest-sz 16 
> --optype aead --silent --ptest throughput --total-ops 1000000
> 
> Not sure if others too faced this issue.
> 
> Thanks,
> Sanjib
> 
> my page-0 wiki
> 
> 
> -----Original Message-----
> From: Trahe, Fiona [mailto:fiona.trahe@intel.com]
> Sent: Tuesday, May 8, 2018 3:26 PM
> To: DAS, SANJIB <sanjib.das@hpe.com>; users@dpdk.org; dts@dpdk.org; 
> test-report@dpdk.org
> Cc: Zhang, Roy Fan <roy.fan.zhang@intel.com>; De Lara Guarch, Pablo 
> <pablo.de.lara.guarch@intel.com>
> Subject: RE: Query on ipsec-secgw with crypto algorithm CCM
> 
> Hi Sanjib,
> 
> Copying Pablo who added unit tests for it in this commit - this should 
> give you an example of how to get it working:
> 77a217a19bb72860e26b9aefb19dce92239e0820
> 
> Also copying Fan who added CCM to aesni_mb PMD.
> 
> Fiona
> 
> > -----Original Message-----
> > From: users [mailto:users-bounces@dpdk.org] On Behalf Of DAS, SANJIB
> > Sent: Wednesday, May 2, 2018 3:21 PM
> > To: users@dpdk.org; dts@dpdk.org; test-report@dpdk.org
> > Cc: DAS, SANJIB <sanjib.das@hpe.com>
> > Subject: [dpdk-users] Query on ipsec-secgw with crypto algorithm CCM
> >
> > Hello team,
> >
> > I am currently executing performance testing using ipsec-secgw 
> > application for different crypto
> algorithms.
> > I was able to execute the tests for crypto algorithms CBC & GCM, but 
> > as such dint find much pointers on CCM.  From ipsec-secgw sample 
> > application source code (DPDK-18.02.1) also it looks CCM support is 
> > not there. Could you kindly share your comments on that. Can we 
> > actually execute ipsec-secgw
> application for crypto algorithm CCM?
> >
> 
> > Thanks,
> > Sanjib
> >
> > my page-0
> > wiki<https://margot.arubanetworks.com/margot/index.php/sanjibdas_wik
> > i_
> > space>
> >
> >
> >
> 

  parent reply	other threads:[~2018-05-16  7:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 14:20 DAS, SANJIB
2018-05-08  9:56 ` Trahe, Fiona
2018-05-09  3:19   ` DAS, SANJIB
2018-05-09 11:52     ` Trahe, Fiona
2018-05-09 12:18       ` DAS, SANJIB
2018-05-16  7:35       ` DAS, SANJIB [this message]
2018-05-16 14:23         ` Trahe, Fiona
2018-05-17  2:41           ` DAS, SANJIB

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=TU4PR8401MB06550B48129357A57B580A918D920@TU4PR8401MB0655.NAMPRD84.PROD.OUTLOOK.COM \
    --to=sanjib.das@hpe.com \
    --cc=dts@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=test-report@dpdk.org \
    --cc=users@dpdk.org \
    /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).