DPDK usage discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Avi Cohen (A)" <avi.cohen@huawei.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: "users@dpdk.org" <users@dpdk.org>,
	"olgas@mellanox.com" <olgas@mellanox.com>
Subject: Re: [dpdk-users] IPsec offload
Date: Wed, 8 Nov 2017 11:17:10 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC467E7@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <B84047ECBD981D4B93EAE5A6245AA361013F1213@FRAEML521-MBX.china.huawei.com>

Hi Avi,

> -----Original Message-----
> From: Avi Cohen (A) [mailto:avi.cohen@huawei.com]
> Sent: Wednesday, November 8, 2017 10:22 AM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Thomas
> Monjalon <thomas@monjalon.net>
> Cc: users@dpdk.org; olgas@mellanox.com
> Subject: RE: [dpdk-users] IPsec offload
> 
> Pablo
> I fixed all issues,  now the app. Is running Just  to clarify one issue:
> I meant that my Ethernet device x540 is capable to do IPsec encryption in
> HW.
> What did you mean "a crypto device (SW or HW)" ?

You are talking about inline crypto there then, which I am not very familiarized.
With crypto device, I mean a lookaside crypto device, such as QAT PMD (example of HW device)
or AESNI MB PMD (examples of SW device).

Regards,
Pablo

> Regards,
> Avi
> 
> > -----Original Message-----
> > From: Avi Cohen (A)
> > Sent: Wednesday, 08 November, 2017 11:21 AM
> > To: 'De Lara Guarch, Pablo'; 'Thomas Monjalon'
> > Cc: 'users@dpdk.org'; 'olgas@mellanox.com'
> > Subject: RE: [dpdk-users] IPsec offload
> >
> > Hi Pablo,
> >
> >  > 1 - Double check you are using the latest IPSec library (0.47) and
> > > that you are linking against it (just follow the documentation).
> >  > 2 - That's a network device, not a crypto device.
> >  [Avi Cohen (A)]
> > 1.  I meant that my Ethernet device x540 is capable to do IPsec
> > encryption in HW.
> >      What did you mean "a crypto device (SW or HW)" ?
> >
> > 2. I  also I enable the IESNI_GCM_PMD according the
> > http://dpdk.org/doc/guides/cryptodevs/aesni_gcm.html ,   but still
> receive this
> > error in init  (: unrecognized input "sa")
> >
> >
> > ./ipsec-secgw -l 20,21 -n 4  --vdev "crypto_aesni_gcm" -- -p 0xf -P -u
> > 0x3 -- config="(0,0,20),(1,0,20),(2,0,21),(3,0,21)" -f ep-sample.cfg
> >
> > EAL: Detected 24 lcore(s)
> > EAL: 16 hugepages of size 1073741824 reserved, but no mounted
> > hugetlbfs found for that size
> > EAL: Probing VFIO support...
> > EAL: PCI device 0000:01:00.0 on NUMA socket 0
> > EAL:   probe driver: 8086:1528 net_ixgbe
> > EAL: PCI device 0000:01:00.1 on NUMA socket 0
> > EAL:   probe driver: 8086:1528 net_ixgbe
> > EAL: PCI device 0000:04:00.0 on NUMA socket 0
> > EAL:   probe driver: 8086:1528 net_ixgbe
> > EAL: PCI device 0000:04:00.1 on NUMA socket 0
> > EAL:   probe driver: 8086:1528 net_ixgbe
> > EAL: PCI device 0000:08:00.0 on NUMA socket 0
> > EAL:   probe driver: 8086:1521 net_e1000_igb
> > EAL: PCI device 0000:08:00.1 on NUMA socket 0
> > EAL:   probe driver: 8086:1521 net_e1000_igb
> > CRYPTODEV: [crypto_aesni_gcm] - Creating cryptodev crypto_aesni_gcm
> >
> > CRYPTODEV: [crypto_aesni_gcm] - Initialisation parameters - name:
> > crypto_aesni_gcm,socket id: 0, max queue pairs: 8, max sessions: 2048
> > Promiscuous mode selected PANIC in parse_cfg_file():
> > ep-sample.cfg:1: error: unrecognized input "sa"
> > 6: [./ipsec-secgw(_start+0x29) [0x44a0f9]]
> > 5: [/lib64/libc.so.6(__libc_start_main+0xf1) [0x7fe3cd492731]]
> > 4: [./ipsec-secgw(main+0xdd) [0x445d2d]]
> > 3: [./ipsec-secgw(parse_cfg_file+0x3d0) [0x44b180]]
> > 2: [./ipsec-secgw(__rte_panic+0xb8) [0x440d83]]
> > 1: [./ipsec-secgw(rte_dump_stack+0x16) [0x4b5876]]
> >
> > Regards
> >  Avi
> >

  reply	other threads:[~2017-11-08 11:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-05  8:32 Avi Cohen (A)
2017-11-06  1:02 ` Thomas Monjalon
2017-11-06 10:25   ` Avi Cohen (A)
2017-11-06 11:13     ` Thomas Monjalon
2017-11-06 15:53       ` Avi Cohen (A)
2017-11-06 16:37         ` De Lara Guarch, Pablo
2017-11-06 16:42           ` Avi Cohen (A)
2017-11-06 16:47             ` De Lara Guarch, Pablo
2017-11-06 17:16               ` Avi Cohen (A)
2017-11-07  9:42                 ` De Lara Guarch, Pablo
2017-11-07  9:49                   ` Avi Cohen (A)
2017-11-07  9:51                     ` De Lara Guarch, Pablo
2017-11-07  8:54               ` Avi Cohen (A)
2017-11-07 11:24                 ` De Lara Guarch, Pablo
2017-11-07 13:36                   ` Avi Cohen (A)
2017-11-07 14:48                     ` De Lara Guarch, Pablo
2017-11-08  8:05                       ` Avi Cohen (A)
2017-11-08  9:20                       ` Avi Cohen (A)
2017-11-08 10:22                       ` Avi Cohen (A)
2017-11-08 11:17                         ` De Lara Guarch, Pablo [this message]
2017-11-08 11:39                           ` Avi Cohen (A)
2017-11-08 11:53                             ` De Lara Guarch, Pablo
2017-11-08 11:50       ` Avi Cohen (A)
2017-11-08 12:20         ` De Lara Guarch, Pablo
2017-11-08 12:39           ` Avi Cohen (A)
2017-11-08 13:26             ` De Lara Guarch, Pablo

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=E115CCD9D858EF4F90C690B0DCB4D8976CC467E7@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=avi.cohen@huawei.com \
    --cc=olgas@mellanox.com \
    --cc=thomas@monjalon.net \
    --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).