From: Ant loves honey <ant_love_honey@yahoo.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK Accelaration Enhancement
Date: Sat, 24 Dec 2016 17:25:58 +0000 (UTC) [thread overview]
Message-ID: <2021242051.1516112.1482600358351@mail.yahoo.com> (raw)
In-Reply-To: <2021242051.1516112.1482600358351.ref@mail.yahoo.com>
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?
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.
Merry Christmas and Happy New Year,
Anthony.
next parent reply other threads:[~2016-12-24 17:26 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 [this message]
2016-12-26 6:02 ` Jain, Deepak K
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=2021242051.1516112.1482600358351@mail.yahoo.com \
--to=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).