From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id A1CADC9C2 for ; Thu, 30 Apr 2015 00:36:26 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP; 29 Apr 2015 15:36:25 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,672,1422950400"; d="scan'208";a="487398909" Received: from pgsmsx101.gar.corp.intel.com ([10.221.44.78]) by FMSMGA003.fm.intel.com with ESMTP; 29 Apr 2015 15:36:24 -0700 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by PGSMSX101.gar.corp.intel.com (10.221.44.78) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 30 Apr 2015 06:36:22 +0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.162]) by shsmsx102.ccr.corp.intel.com ([10.239.4.154]) with mapi id 14.03.0224.002; Thu, 30 Apr 2015 06:36:22 +0800 From: "Zhou, Danny" To: "James (Fei) Liu-SSI" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Issues of MSIx interrupt enable with user space driver Thread-Index: AQHQgf144QHvEesiRkOMFxvdtP0IsZ1jDizggAC7gACAAMhvYA== Date: Wed, 29 Apr 2015 22:36:21 +0000 Message-ID: References: <99767EA2E27DD44DB4E9F9B9ACA458C03B30F07F@SSIEXCH-MB3.ssi.samsung.com> <99767EA2E27DD44DB4E9F9B9ACA458C03B30F401@SSIEXCH-MB3.ssi.samsung.com> In-Reply-To: <99767EA2E27DD44DB4E9F9B9ACA458C03B30F401@SSIEXCH-MB3.ssi.samsung.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Issues of MSIx interrupt enable with user space driver X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2015 22:36:27 -0000 DPDK is aimed to drive PCIe NIC device for high performance packet processi= ng only. While we do have a Waikiki Beach project that integrates user space DPDK PMD and NVMe poll mode iSCSI target and NVMe bac= kend together to improve performance of storage. > -----Original Message----- > From: James (Fei) Liu-SSI [mailto:james.liu@ssi.samsung.com] > Sent: Thursday, April 30, 2015 2:26 AM > To: Zhou, Danny; dev@dpdk.org > Cc: Liang, Cunming > Subject: RE: [dpdk-dev] Issues of MSIx interrupt enable with user space d= river >=20 > Hi Danny, >=20 > Thanks a lot for your promptly answer. I am going to check your patch = soon. In the mean time, Have you guys ever try DPDK > with PCIe storage device? >=20 > Regards, > James >=20 > -----Original Message----- > From: Zhou, Danny [mailto:danny.zhou@intel.com] > Sent: Tuesday, April 28, 2015 4:19 PM > To: James (Fei) Liu-SSI; dev@dpdk.org > Cc: Liang, Cunming > Subject: RE: [dpdk-dev] Issues of MSIx interrupt enable with user space d= river >=20 > The V6 "Interrupt PMD" patch has been sent out to DPDK.org 2 months ago, = and V7 is under development with changes to > include more generic APIs that could support all kinds of interrupts (e.g= . HW Rx interrupt and SW ring interrupt). >=20 > Stay tuned. >=20 > > -----Original Message----- > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of James (Fei) > > Liu-SSI > > Sent: Wednesday, April 29, 2015 5:58 AM > > To: dev@dpdk.org > > Subject: [dpdk-dev] Issues of MSIx interrupt enable with user space > > driver > > > > Hi All, > > We are porting driver from kernel into user space driver with DPDK > > for one of our devices. Polling thread works fine without any issue. > > However, we want to switch from polling to interrupt based handler. Whi= le we enable interrupt with VFIO MSIx, we always get > below errors after issuing one command: > > > > [ 465.464186] dmar: DRHD: handling fault status reg 2 [ 465.464194] > > dmar: INTR-REMAP: Request device [[02:00.0] fault index 27 [ > > 465.464194] INTR-REMAP:[fault reason 34] Present field in the IRTE > > entry is clear > > > > Here are steps we follow to enable interrupt: > > 1. --vfio-intr msix was passed in as parameter for rte_eal_init > > 2. rte_intr_enable was called during the drive probe stage. > > 3. rte_intr_callback_register was called after interrupt was enabled > > > > > > > > Is there anyone in the forum who worked on the interrupt handler to > > share with us about your comments? thanks for your help in advance. > > > > Regards, > > James > >