DPDK is aimed to drive PCIe NIC device for high performance packet processing only. While we do have a Waikiki Beach project that integrates user space DPDK PMD and NVMe poll mode iSCSI target and NVMe backend together to improve performance of storage.
> -----Original Message----- > From: James (Fei) Liu-SSI [mailto:james.liu at ssi.samsung.com] > Sent: Thursday, April 30, 2015 2:26 AM > To: Zhou, Danny; dev at dpdk.org > Cc: Liang, Cunming > Subject: RE: [dpdk-dev] Issues of MSIx interrupt enable with user space driver > > Hi Danny, > > 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? > > Regards, > James > > -----Original Message----- > From: Zhou, Danny [mailto:danny.zhou at intel.com] > Sent: Tuesday, April 28, 2015 4:19 PM > To: James (Fei) Liu-SSI; dev at dpdk.org > Cc: Liang, Cunming > Subject: RE: [dpdk-dev] Issues of MSIx interrupt enable with user space driver > > 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). > > Stay tuned. > > > -----Original Message----- > > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of James (Fei) > > Liu-SSI > > Sent: Wednesday, April 29, 2015 5:58 AM > > To: dev at 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. While > > 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 > >
