From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nm19-vm0.bullet.mail.bf1.yahoo.com (nm19-vm0.bullet.mail.bf1.yahoo.com [98.139.213.162]) by dpdk.org (Postfix) with ESMTP id 9329F282 for ; Mon, 26 Dec 2016 07:19:23 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1482733162; bh=tTzHPwsM/sH9rD4CNVmX0EGZi/3KG2l4Q/1dN2/yqDI=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=sa9N7iYRGtjdK4Jsa1xI0ZGc3IHQmVYl9IWIB8fMxHOj/dsJ0dPvgeAPPawHqXeJKVG+79+fVOcomVpNf1t3ZtLCeLOxORLhpnpyyBHJxvNn4j6B2H+IkypHw62L/DYgmZcVYu1Hncfn2lm00lIa9ucUpVjFJmGq0jzo3FXR+DX8p6sxYu1FIol7gIUnZx9ctYzjWg1LoIoNC780DvI6LY/SauFK/MeoxnBXOLUsCWKKW04w71P+G57s0R6HCCSet2Gb58xChUI3VyGokjLS8XnVUet5LnNvFRY/QmAGi/DO27g3MnFusu2CYU0r5e//bsTeLqTW1p8Wj5PP1UnPNQ== Received: from [98.139.170.182] by nm19.bullet.mail.bf1.yahoo.com with NNFMP; 26 Dec 2016 06:19:22 -0000 Received: from [98.139.212.206] by tm25.bullet.mail.bf1.yahoo.com with NNFMP; 26 Dec 2016 06:19:22 -0000 Received: from [127.0.0.1] by omp1015.mail.bf1.yahoo.com with NNFMP; 26 Dec 2016 06:19:22 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 805979.5046.bm@omp1015.mail.bf1.yahoo.com X-YMail-OSG: W0KDwZkVM1nRrd2DmRWCf6Nr5T8QcsADKv6ZFzJbBuMmyPpj.WP1.QAizO5Y2TC NsTkHYeFViiajWwsUaKS96fmNk8_tP.0z3AuH85Y36eINAtCb3.QEmhF5KSPhDX45mgVVR6eGoii 5HHBgXrRmwRjKRJnsi9R_gS6PEXgAn5224J1kQnIINJH9horDxHWtIzivg.uH9xH.f23RAbgY34y 648YQvc_Tga_C_8q1pfQ2aZmnSkDYipgMcylwhHPji8hwsvkynFYNVCzbW3gailV5n9xYF7.1AUG polhx2AE28DKpfliaxSvDsEvTsOQiZHke.Uo6wqfl0UOovCKqSIMz0qT9oVji69HWW9CtePqy6TD aJiY2M6dUdor4QDwM.HQX5FSw988Na41QX_CKFmyAKiW3eLC35uZUp5qzl4ZTCbOAG5c9hGP3hkl vQ0V2tqTo3CNS1ECCKkw_WdLOD0BePN3EkiJQ_QLxOMngS0arwDFGm5zkEfvMugqEtabvfa6DaVs 7DFELqHNG8Q.oHf2FKmjLZTf2BUTqiLFA3.hI Received: from jws400084.mail.bf2.yahoo.com by sendmailws105.mail.bf1.yahoo.com; Mon, 26 Dec 2016 06:19:22 +0000; 1482733162.414 Date: Mon, 26 Dec 2016 06:19:22 +0000 (UTC) From: Ant loves honey To: "Jain, Deepak K" , "dev@dpdk.org" Message-ID: <1528264043.1886486.1482733162163@mail.yahoo.com> In-Reply-To: References: <2021242051.1516112.1482600358351.ref@mail.yahoo.com> <2021242051.1516112.1482600358351@mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] DPDK Accelaration Enhancement X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ant loves honey List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2016 06:19:24 -0000 Deepak, The .../doc/guides/cryptodevs/qat.rst is geared toward crypto and no mentio= n of compression. 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 initializ= ation since the Intel QAT can support compression. It seems to me IP payload can make good use of the hardware assisted compre= ssion and this will be a nice feature to have. Thanks so much, anthony. From: "Jain, Deepak K" To: Ant loves honey ; "dev@dpdk.org" =20 Sent: Sunday, December 25, 2016 10:02 PM Subject: RE: [dpdk-dev] DPDK Accelaration Enhancement =20 HI Anthony, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ant loves honey > Sent: Saturday, December 24, 2016 10:56 PM > To: dev@dpdk.org > Subject: [dpdk-dev] DPDK Accelaration Enhancement >=20 > Currently DPDK has the crypto PMD (.../drivers/crypto/qat/) and example > code (.../examples/dpdk_qat). > Intel QuickAssist Technology also supports compression along with > crypto.=C2=A0 Last weekend, there is a proposed project to Intel Dev Mesh= - "A > VPP plugin utilizing Intel QucikAssist Technology to perform hardware > assisted compression operations" >=20 > https://devmesh.intel.com/projects/a-vpp-plugin-utilizing-intel-quickassi= st- > technology-to-perform-hardware-assisted-compression-operation >=20 > Do we need a new PMD driver for compression or should we modify the > exiting crypto/qat driver to also support compression? There is still NO compression support in DPDK which utilizes Intel(R) Quick= Assist Technology. >=20 > The Intel QAT driver should be present in any Linux kernel greater than > version 4.4 >=20 > 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 t= he > code level. > Any pointer on how to move forward is greatly appreciated. > Please also let me know if I should modify the proposed project. >=20 Have you gone through the Crypto Documentation on dpdk.org and release note= s (qat.rst) for more information? > Merry Christmas and Happy New Year, > Anthony. Regards, Deepak =20 >From yuanhan.liu@linux.intel.com Mon Dec 26 07:25:34 2016 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 4FFC398 for ; Mon, 26 Dec 2016 07:25:34 +0100 (CET) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga101.jf.intel.com with ESMTP; 25 Dec 2016 22:25:33 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,404,1477983600"; d="scan'208";a="1086663544" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by fmsmga001.fm.intel.com with ESMTP; 25 Dec 2016 22:25:32 -0800 Date: Mon, 26 Dec 2016 14:27:19 +0800 From: Yuanhan Liu To: Jianfeng Tan Cc: dev@dpdk.org, ferruh.yigit@intel.com, cunming.liang@intel.com Message-ID: <20161226062719.GA19288@yliu-dev.sh.intel.com> References: <1480689075-66977-1-git-send-email-jianfeng.tan@intel.com> <1482477266-39199-1-git-send-email-jianfeng.tan@intel.com> <1482477266-39199-3-git-send-email-jianfeng.tan@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1482477266-39199-3-git-send-email-jianfeng.tan@intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH v2 2/7] net/virtio_user: postpone DRIVER OK notification X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2016 06:25:34 -0000 On Fri, Dec 23, 2016 at 07:14:21AM +0000, Jianfeng Tan wrote: > In driver probe phase, we obtain device information; and then virtio > driver will initialize device and stores info, like negotiated > features, in vhost_user layer; finally, vhost_user gets DRIVER_OK > notification from virtio driver, and then sync with backend device. > > Previously, DRIVER_OK could be sent twice: 1. when ether layer invokes > eth_device_init to initialize device; 2. when user configures it with > different configuration from that of previous. Yes, but that's wrong. Now only 1) will be taken. > Since we can only depend on DRIVER_OK notification to sync with backend > device, we postpone it to virtio_dev_start when everything is settled. I don't quite understand what you were going to fix here; you don't state it in the commit log after all. Normally, when everything is negotiated (when DRIVER_OK is set), we should not set it again, unless a reset has been happened. If you look at QEMU, qemu will simply ignore it once vhost has already started. --yliu