DPDK usage discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Pankaj Joshi <pankaj.joshi63@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] [dpdk-dev] Problem running dpdk-qat example in	SR-IOV mode
Date: Thu, 23 Feb 2017 16:18:13 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476E1582@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <5068483.Xs10W06zQs@xps13>

Hi Thomas,

> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Thomas
> Monjalon
> Sent: Monday, February 20, 2017 1:11 PM
> To: Trahe, Fiona
> Cc: dev@dpdk.org; Pankaj Joshi; users@dpdk.org
> Subject: Re: [dpdk-users] [dpdk-dev] Problem running dpdk-qat example in
> SR-IOV mode
> 
> 2017-02-20 11:53, Trahe, Fiona:
> > From: Pankaj Joshi
> > >
> > > Hello All,
> > >
> > > I am trying to run dpdk-qat example code in SR-IOV mode. Steps done
> by me
> > > so far are :
> >
> > The dpdk-qat example app is an earlier mechanism of wrapping a QAT
> driver into DPDK - it's not using the cryptodev API, and depends on both a
> kernel driver and user-space libs from a QAT package.
> > Unless you have a really good reason for using this (like you wanted to
> use the older Cave Creek device) I would recommend you use the cryptodev
> API.
> 
> Could we remove this obsolete example?

This is a good point. How can we proceed with this? As it is a sample application,
does it require a deprecation notice?

Thanks,
Pablo

  reply	other threads:[~2017-02-23 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20 11:11 [dpdk-users] " Pankaj Joshi
2017-02-20 11:53 ` [dpdk-users] [dpdk-dev] " Trahe, Fiona
2017-02-20 13:10   ` Thomas Monjalon
2017-02-23 16:18     ` De Lara Guarch, Pablo [this message]
2017-02-23 16:43       ` 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=E115CCD9D858EF4F90C690B0DCB4D897476E1582@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=pankaj.joshi63@gmail.com \
    --cc=thomas.monjalon@6wind.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).