From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Chinmaya Dwibedy <ckdwibedy@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Questions on ipsec-secgw sample application and DPDK’s crypto framework
Date: Tue, 17 May 2016 11:57:44 +0100 [thread overview]
Message-ID: <beccee8e-af1f-e959-c220-23062c5c819f@intel.com> (raw)
In-Reply-To: <CAMHS8RG4DLF1zWJDnzB0DtygNPzdJ3o0VsL=60JVNvKxhfBXWg@mail.gmail.com>
Hi,
IPSec app can run with or without QAT.
DPDK Cryptodev also has Software encryption for those platforms without
Crypto Hardware offloads.
AES-NI MB and GCM PMDs are examples of Software Cryptodevs.
I suggest that you read the following documentation for more details:
http://dpdk.org/doc/guides/cryptodevs/index.html
To run DPDK IPSec app in a VM using QAT PMD, at the moment you would
need a Linux kernel 4.4+, create your QAT VFs, then assign the VFs to
your VM.
If you are having problems, I would recommend that you run on the host
first if possible.
Sergio
On 17/05/2016 10:10, Chinmaya Dwibedy wrote:
> Hi All,
>
>
> Can the ipsec-secgw sample application (
> http://dpdk.org/browse/dpdk/tree/examples/ipsec-secgw) be run on VM which
> has access to Intel® QuickAssist Technology hardware device? Please
> clarify. Note: both the DPDK package and the QuickAssist Technology
> Software Library installed on this VM.
>
>
> What I understand, we need not to call Intel QuickAssist Technology
> Cryptographic API () for crypto operation (encryption, decryption,
> authentication processing). The DPDK’s crypto framework and QAT PMD (driver
> for Intel’s QuickAssist Technology device) takes care of them. Please
> correct me if I am wrong.
>
>
>
> Regards,
>
> Chinmaya
prev parent reply other threads:[~2016-05-17 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 9:10 Chinmaya Dwibedy
2016-05-17 10:57 ` Sergio Gonzalez Monroy [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=beccee8e-af1f-e959-c220-23062c5c819f@intel.com \
--to=sergio.gonzalez.monroy@intel.com \
--cc=ckdwibedy@gmail.com \
--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).