From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: Problem running dpdk-qat example in SR-IOV mode Date: Mon, 20 Feb 2017 14:10:39 +0100 Message-ID: <5068483.Xs10W06zQs@xps13> References: <348A99DA5F5B7549AA880327E580B4358918EF1F@IRSMSX101.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Pankaj Joshi , users@dpdk.org To: "Trahe, Fiona" Return-path: Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by dpdk.org (Postfix) with ESMTP id 25A45374E for ; Mon, 20 Feb 2017 14:10:41 +0100 (CET) Received: by mail-wm0-f53.google.com with SMTP id r141so52176056wmg.1 for ; Mon, 20 Feb 2017 05:10:41 -0800 (PST) In-Reply-To: <348A99DA5F5B7549AA880327E580B4358918EF1F@IRSMSX101.ger.corp.intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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?