From: "Jain, Deepak K" <deepak.k.jain@intel.com>
To: Ant loves honey <ant_love_honey@yahoo.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Accelaration Enhancement
Date: Mon, 26 Dec 2016 06:02:25 +0000 [thread overview]
Message-ID: <A09C9DDE180C7E429EC68E2BFB95C903395024EA@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <2021242051.1516112.1482600358351@mail.yahoo.com>
HI Anthony,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ant loves honey
> Sent: Saturday, December 24, 2016 10:56 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] DPDK Accelaration Enhancement
>
> Currently DPDK has the crypto PMD (.../drivers/crypto/qat/) and example
> code (.../examples/dpdk_qat).
> Intel QuickAssist Technology also supports compression along with
> crypto. Last weekend, there is a proposed project to Intel Dev Mesh - "A
> VPP plugin utilizing Intel QucikAssist Technology to perform hardware
> assisted compression operations"
>
> https://devmesh.intel.com/projects/a-vpp-plugin-utilizing-intel-quickassist-
> technology-to-perform-hardware-assisted-compression-operation
>
> Do we need a new PMD driver for compression or should we modify the
> exiting crypto/qat driver to also support compression?
There is still NO compression support in DPDK which utilizes Intel(R) QuickAssist Technology.
>
> The Intel QAT driver should be present in any Linux kernel greater than
> version 4.4
>
> I am trying to put the pieces together and hitting a roadblock. I am also
> figuring how the PMD driver is interacting with the Intel QAT driver at the
> code level.
> Any pointer on how to move forward is greatly appreciated.
> Please also let me know if I should modify the proposed project.
>
Have you gone through the Crypto Documentation on dpdk.org and release notes (qat.rst) for more information?
> Merry Christmas and Happy New Year,
> Anthony.
Regards,
Deepak
next prev parent reply other threads:[~2016-12-26 6:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2021242051.1516112.1482600358351.ref@mail.yahoo.com>
2016-12-24 17:25 ` Ant loves honey
2016-12-26 6:02 ` Jain, Deepak K [this message]
2016-12-26 6:19 ` Ant loves honey
2017-01-02 15:54 ` Thomas Monjalon
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=A09C9DDE180C7E429EC68E2BFB95C903395024EA@IRSMSX107.ger.corp.intel.com \
--to=deepak.k.jain@intel.com \
--cc=ant_love_honey@yahoo.com \
--cc=dev@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).