From: Naveen Kumar <Naveen.Kumar@commagility.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] QAT crypto driver: rte_security crypto offload
Date: Mon, 3 Feb 2020 11:52:20 +0000 [thread overview]
Message-ID: <572acbd6a9fd4094bcaeeb26534f3dd2@de-mta1.commagility.com> (raw)
Hello,
Is there a roadmap for "rte_security" based crypto offload support in QAT crypto driver?
Regards,
Naveen
--
Naveen Kumar
Senior Engineer
See us at MWC - Booth 7B14
CommAgility is a Wireless Telecom Group company
T: +49 (0)203 306 4537 | www.commagility.com
Registered in England, Company No. 05914025. VAT No. DE299686390
CommAgility is an ISO 9001:2015-certified company
This email is confidential, for recipient’s use only.
reply other threads:[~2020-02-03 11:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=572acbd6a9fd4094bcaeeb26534f3dd2@de-mta1.commagility.com \
--to=naveen.kumar@commagility.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).