From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f68.google.com (mail-it0-f68.google.com [209.85.214.68]) by dpdk.org (Postfix) with ESMTP id 9643B101B; Tue, 28 Mar 2017 08:01:38 +0200 (CEST) Received: by mail-it0-f68.google.com with SMTP id 76so1479738itj.0; Mon, 27 Mar 2017 23:01:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3JJKlcvggRj80/VPE6HxlzgFwnbwbdgM8Izxpl+MROU=; b=RWL85h9EUdk0eEZ5ufbUenr27Kv8XQWnMtu8ZntCW+8aQ7ps8NVxdl8aA92IZHul7f PPPI9GmyjmI/JcCvvEgy5xcdlpLmSU/i12aGQcXrF4UkVJ5NwIIgG2vioE3RjN1xR6y2 u2bigBKtTeiwkng9AadobZhw8jnAglVaXKPuoxYhHz9wCEAbHZxiy66xlkzqB0edudlB BBUz1zMAEH4y+O8y7l+cSHrSpR1zusT1DVDO+wFmH3vmFTg+N4bSP7kvtFsUHTMQ26Nb WT/CZN+KvDceI6tp4oKuNBzhiMrmMphOmZzb3cakLANEXXwGvVFIbVaNWuDf2U/Vl8Ak PclQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3JJKlcvggRj80/VPE6HxlzgFwnbwbdgM8Izxpl+MROU=; b=nVqvRMeBXgEcMtNRc10MXGP+F69WQQQI+2eFx3KSXxn8XdkiAq5rjOrW5jE79R15AD WI+o7qeDvgi4ciIQogiNz87iZJXfc4V1GHszhCh/JqU6Yu3o7p5vqY9KCLRBKpx8zGub pGX89RKXeJGMxKjmFS4Ch24N2oeUDfvjRZIc+wAcHGEUYbNtW/VKRLRGmBXaUExicT+a 4KyJgm4bkgvN3PH43QoMY3CBMF+wXtzfNm+9m99l12qQ1RmpV/T1NlKnpH6b9Ido/kwo f+S8wKXEh2Wox6hhXjWwAzidecXjHS+YmR4qS91rQdiQbEhrOLowSgcMrWiN/Qry/QPJ YzOA== X-Gm-Message-State: AFeK/H3PNiiaM53/HVccFq49xaY0nFgkMTPc/H4zBtln0qKboP52oZZ0Arq0ppT6fSCxkmK5UwUqD1rF9dO1QA== X-Received: by 10.107.46.24 with SMTP id i24mr28530835ioo.84.1490680897429; Mon, 27 Mar 2017 23:01:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.110.201 with HTTP; Mon, 27 Mar 2017 23:01:37 -0700 (PDT) In-Reply-To: <348A99DA5F5B7549AA880327E580B435891D112C@IRSMSX101.ger.corp.intel.com> References: <348A99DA5F5B7549AA880327E580B435891D112C@IRSMSX101.ger.corp.intel.com> From: Pankaj Joshi Date: Tue, 28 Mar 2017 11:31:37 +0530 Message-ID: To: "Trahe, Fiona" Cc: qat-linux , "dev@dpdk.org" , "users@dpdk.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] [dpdk-dev] Query for QAT software running in SR-IOV mode at VM X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2017 06:01:38 -0000 Hello Fiona, Thanks for giving response. Below are my some points. Yes,I am using the cpaCyXXX API's so I need steps 4,5,6,7 here. Without SR-IOV, with "ICP_WITHOUT_IOMMU" application is running fine. Here I am trying to run my application on VM with SR-IOV enabled mode. Also I have pass through VM devices to VM and binded those devices to vfio-pci as given in section 10.6. So trying to get response through registered callback function. Regards, Pankaj Joshi On Mon, Mar 27, 2017 at 10:44 PM, Trahe, Fiona wrote: > Hi Pankaj, > See below > > > -----Original Message----- > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pankaj Joshi > > Sent: Monday, March 27, 2017 5:20 PM > > To: qat-linux ; dev@dpdk.org; users@dpdk.org > > Subject: [dpdk-dev] Query for QAT software running in SR-IOV mode at VM > > > > Hello Team, > > > > I have followed the steps given in section 10.4 in below link : > > > > > > > > http://dpdk.org/doc/guides/cryptodevs/qat.html > > > > > > > > > > > > > > > > > > > > 1. Export ICP_WITHOUT_IOMMU=1, and install the QAT software in > > host ( SR-IOV mode ). > > > > 2. Checked that there are 32 VF devices are there. > > > > 3. Launched VM and add 1 PCI device to the VM. > > > > 4. 1 device map to 1 /etc/dh895xcc_qa_dev0.conf file which is > having > > 2 instance. > > > > 5. Install QAT software in VM m/c with guest mode as explained in > > below link. > > > > 6. Running my application, it is able to submit the request to > hardware > > queue using API,cpaCySymDpEnqueueOp. > > > > 7. But unable to call the registered callback function. > > > > http://www.intel.com/content/dam/www/public/us/en/documents/applicati > > on-notes/virtualization-technology-with-quickassist- > technology-app-note.pdf > > > > How I can debug the issue, or how I enable the logs in QAT software. > > > If you're trying to use QAT with DPDK cryptodev API then there's no need > for steps 4,5,6,7 > above. These are steps for using the QA API, i.e. cpaCyXXX APIs. > > Also the ICP_WITHOUT_IOMMU condition is only needed if intending to access > the QAT HW from > the Host. If you intend to access the crypto services on QAT via the VF on > a VM, then you can > use the standard out of the box install for a HOST. > > Once the VF device is passed through to the VM, on the VM it can be passed > straight through > to the user-space DPDK QAT PMD without a QAT kernel driver. > i.e. follow the bind commands on http://dpdk.org/doc/guides/ > cryptodevs/qat.html > to bind the VF to either igb_uio or vfio-pci > > Then build your application to use the cryptodev APIs, see > http://dpdk.org/doc/guides/sample_app_ug/ipsec_secgw.html > for an example of how to do this. > If you just want to get it up and running without a traffic generator, you > can use the test app to > run a sanity check against any of the crypto poll mode drivers, e.g. to > run some basic functional tests > against the QAT PMD, e.g. > use dpdk/usertools/dpdk-setup.sh to allocate huge pages > start test app, e.g. test -n1 -l1 > (The test app has moved in a recent release, you should find it at either > dpdk/build/app/ or dpdk/build/build/test/test ) > Run the qat test suite with > >cryptodev_qat_autotest > > > > Please help here. > > > > Regards, > > > > Pankaj Joshi >