DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ant loves honey <ant_love_honey@yahoo.com>
Cc: dev@dpdk.org, "Jain, Deepak K" <deepak.k.jain@intel.com>
Subject: Re: [dpdk-dev] DPDK Accelaration Enhancement
Date: Mon, 02 Jan 2017 16:54:47 +0100	[thread overview]
Message-ID: <9279014.99l058OOxo@xps13> (raw)
In-Reply-To: <1528264043.1886486.1482733162163@mail.yahoo.com>

2016-12-26 06:19, Ant loves honey:
> I am trying to figure out what it takes to have compression
> support on DPDK such as new PMD driver, additional defines
> and/or API or chipset initialization since the Intel QAT can
> support compression.

You need to solve 2 new things in DPDK:
- introduce a generic compression API
- be able to use a QAT device with a compression driver while
being used with a crypto driver

Interesting work to do :)

      reply	other threads:[~2017-01-02 15:54 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
2016-12-26  6:19     ` Ant loves honey
2017-01-02 15:54       ` Thomas Monjalon [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=9279014.99l058OOxo@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=ant_love_honey@yahoo.com \
    --cc=deepak.k.jain@intel.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).