From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sam Subject: Re: Dpdk ixgbe driver bug? Date: Wed, 27 Sep 2017 11:58:50 +0800 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" To: dev@dpdk.org Return-path: Received: from mail-qk0-f174.google.com (mail-qk0-f174.google.com [209.85.220.174]) by dpdk.org (Postfix) with ESMTP id 911C1532D for ; Wed, 27 Sep 2017 05:58:51 +0200 (CEST) Received: by mail-qk0-f174.google.com with SMTP id r141so12144549qke.2 for ; Tue, 26 Sep 2017 20:58:51 -0700 (PDT) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" switch means hardware switch attach this PC, not ovs-dpdk 2017-09-27 11:57 GMT+08:00 Sam : > Hi all, > > I'm running ovs-dpdk using ixgbe driver with sriov mode. My topology is: > vf(ens16) and pf(eth0) is from netdevice 1; vf(ens161) and pf(eth1) is from > netdevice 2. Then linux kernel driver bond ens16 and ens161 into bond1, > ovs-dpdk bond eth0 and eth1 into dpdkb2 as ovs-dpdk port. > > I found that, the ovs-dpdk running for about half month, the bond1 and > dpdkb2 port will block and no packets could pass through, then I have to > restart ovs-dpdk, then it's OK. > > I think there is bug in ixgbe vf/pf driver, as I use standard ovs-dpdk, > and when bug happen, I could not capture packet on dond1 by tcpdump. And > the switch is OK, so the packet could only block or drop in ixgbe vf/pf > driver. > > How to fix this bug? Thank you~ >