From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f65.google.com (mail-it0-f65.google.com [209.85.214.65]) by dpdk.org (Postfix) with ESMTP id E6065968 for ; Tue, 12 Jul 2016 14:00:40 +0200 (CEST) Received: by mail-it0-f65.google.com with SMTP id u186so851574ita.1 for ; Tue, 12 Jul 2016 05:00:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eZUsO3gvLDpCNZB4OqqeawyOIoSNrYURtbSRCTZyd4A=; b=Nmn15AZOQ/pgDAyj2fx+B8A67Qr8EEm5H6JH7Z45aRNLUVRceLDuZoUPRzqUpuIRMI YqNxbkYHx8+o0TTIFl32J1XdPm1LoceqHEsT/DVuTOwkj42czUDUbF3VhTByZA8nJtLx j/ENcUFW3l3+3HPAysZnPVbil7yp9YmqwqgGRz3nDX1BYYdYFjTlS40suP2iiFiebW1u wBlua+k4orZNbyY9SdOFwyu1kjD9Mk+bjbPH7+Y8+huNegNV2C60HaqFyrHPA6mtV+I9 H95dOS8QKbHo2+4yxORdE7AQpqswEXNcQvBC/jth+Sexeav4C7zATjs0BQQZephYNw62 9RKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eZUsO3gvLDpCNZB4OqqeawyOIoSNrYURtbSRCTZyd4A=; b=PFZIHZ9gqq+k0s1tbzyZK1l4NpZxQQiitlv+fO6CitLh7QXeOTPAfWxZUAbzjzDT97 9j9DWiyOanRvpU31ABo2pg4vkzyryoA6oZ+eykXdpRFnz38yeaCkl4h03dPBAnYMPLyt Wf3dnwOkN3CMcUTHSF1zvgInEt9OL1pxVoryyZ4NH/8QiTiV5bJTcabYJO4ApegfAwqZ xkTj5fLTfv2LMzFaxqBEoNEK5DVce5Z6uja4prkeyZ7JpZ99PyCgSN1DwWSQQT43IjyC H4Ze8dPNr5K0fq/9nF3he/vm+G66xH9txYno+D+zHTfBW6O06cIFDLRzFG8xHxM1xpFC xVsA== X-Gm-Message-State: ALyK8tJzpaJhqtyhcgD6Qa32frqgJUolP9vCj+8Rjm0R6EmtisQ0wU7yI6M37koGTF+C4K1rvdtoDEcPxa0e8Q== X-Received: by 10.36.230.5 with SMTP id e5mr2447875ith.92.1468324840343; Tue, 12 Jul 2016 05:00:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.46.223 with HTTP; Tue, 12 Jul 2016 05:00:39 -0700 (PDT) In-Reply-To: References: From: Bill Bonaparte Date: Tue, 12 Jul 2016 20:00:39 +0800 Message-ID: To: Jay Rolette Cc: DPDK 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] Help: How to read packet statistics from device registers via dpdk PMD? 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: Tue, 12 Jul 2016 12:00:41 -0000 Hi, Jay: My apologies for taking me to get back to you. I tried the sample apps on my environment follow your advice, and I found it works well. so I started to compare the code related to the api between my app and the sample app, I didn't find any significative difference. I am very confused. ..... finnaly, with the help of my colleague, I tracked down the problem. It's a confused character of my platform that make the packets miss the interface which I monitored. so I can access the IP of the interface, but the flow don't pass through the interface. after ajusting the topology, the api works well. anyhow, thanks to your advice, I tracked down the problem. so again, I appreciate your time in talking with me about this api. On Thu, Jul 7, 2016 at 8:19 PM, Jay Rolette wrote: > > On Thu, Jul 7, 2016 at 12:52 AM, Bill Bonaparte > wrote: > >> I am so happy to get your reply. >> My dpdk version is 2.1=EF=BC=8Cand the OS is centOS 7=E3=80=82 >> the following is the output from "dpdk_nic_bind.py --status": >> >> [root@APV35 ~]# dpdk_nic_bind.py --status >> >> Network devices using DPDK-compatible driver >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> 0000:04:00.0 'VMXNET3 Ethernet Controller' drv=3Digb_uio unused=3D >> 0000:0b:00.0 'VMXNET3 Ethernet Controller' drv=3Digb_uio unused=3D >> 0000:13:00.0 'VMXNET3 Ethernet Controller' drv=3Digb_uio unused=3D >> 0000:1b:00.0 'VMXNET3 Ethernet Controller' drv=3Digb_uio unused=3D >> >> Network devices using kernel driver >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> 0000:03:00.0 'VMXNET3 Ethernet Controller' if=3Dens160 drv=3Dvmxnet3 >> unused=3Digb_uio *Active* >> >> Other network devices >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >> > > That's a different virtual NIC than what I'm running in my VMs, but given > your app isn't working directly on the hardware, I doubt that's the issue= . > In case it helps along the way, here's what I see in my VM: > > $ dpdk_nic_bind.py --status > > Network devices using DPDK-compatible driver > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 0000:02:02.0 '82545EM Gigabit Ethernet Controller (Copper)' drv=3Digb_uio > unused=3D > 0000:02:03.0 '82545EM Gigabit Ethernet Controller (Copper)' drv=3Digb_uio > unused=3D > 0000:02:04.0 '82545EM Gigabit Ethernet Controller (Copper)' drv=3Digb_uio > unused=3D > 0000:02:05.0 '82545EM Gigabit Ethernet Controller (Copper)' drv=3Digb_uio > unused=3D > > Network devices using kernel driver > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 0000:02:01.0 '82545EM Gigabit Ethernet Controller (Copper)' if=3Deth0 > drv=3De1000 unused=3Digb_uio *Active* > > Other network devices > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > >> I tried it on the physical mathine, it still does not work. the OS is >> centOS 7, too. >> [root@AN ~]# dpdk_nic_bind.py --status >> >> Network devices using DPDK-compatible driver >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> 0000:01:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=3Digb_= uio >> unused=3D >> 0000:01:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=3Digb_= uio >> unused=3D >> 0000:03:00.0 'I350 Gigabit Backplane Connection' drv=3Digb_uio unused=3D >> 0000:03:00.1 'I350 Gigabit Backplane Connection' drv=3Digb_uio unused=3D >> 0000:03:00.2 'I350 Gigabit Backplane Connection' drv=3Digb_uio unused=3D >> 0000:03:00.3 'I350 Gigabit Backplane Connection' drv=3Digb_uio unused=3D >> 0000:07:00.0 'I350 Gigabit Network Connection' drv=3Digb_uio unused=3D >> 0000:07:00.1 'I350 Gigabit Network Connection' drv=3Digb_uio unused=3D >> 0000:07:00.2 'I350 Gigabit Network Connection' drv=3Digb_uio unused=3D >> 0000:07:00.3 'I350 Gigabit Network Connection' drv=3Digb_uio unused=3D >> 0000:09:00.0 'I350 Gigabit Network Connection' drv=3Digb_uio unused=3D >> 0000:09:00.1 'I350 Gigabit Network Connection' drv=3Digb_uio unused=3D >> 0000:09:00.2 'I350 Gigabit Network Connection' drv=3Digb_uio unused=3D >> 0000:09:00.3 'I350 Gigabit Network Connection' drv=3Digb_uio unused=3D >> 0000:0c:00.0 'Device 0011' drv=3Digb_uio unused=3D >> 0000:0f:00.1 'I350 Gigabit Network Connection' drv=3Digb_uio unused=3D >> >> Network devices using kernel driver >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> 0000:0f:00.0 'I350 Gigabit Network Connection' if=3Denp15s0f0 drv=3Digb >> unused=3Digb_uio *Active* >> >> Other network devices >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >> > > With it not working on hardware and you having devices successfully bound > to DPDK, maybe it's a problem in your app. Have you tried running any of > the sample apps that use rte_eth_stats_get() and see if it works there? > > Jay > > >> On Tue, Jul 5, 2016 at 8:03 PM, Jay Rolette wrote: >> >>> >>> On Tue, Jul 5, 2016 at 2:35 AM, Bill Bonaparte >>> wrote: >>> >>>> Hi: >>>> I am a new fish, I have tried my best to find answer about my question >>>> on >>>> web, but I failed. so >>>> I come here to ask for your help. the below is my question: >>>> >>>> I found that dpdk provides a api rte_eth_stats_get to read packet >>>> statistics about the interface, includes total input/output >>>> unicast/multicast/brodcast packets/bytes. but the api does not work on >>>> VMxnet interface (which is a virtual interface in VMware machine). >>>> >>> >>> Probably something in your app or environment rather than in the API >>> itself. We run rte_eth_stats_get() against interfaces in VMware Fusion, >>> VirtualBox and real hardware and they all work generally. >>> >>> Need some info before anyone can help you much: >>> >>> * What version of DPDK are you running? >>> * What OS are you running on? >>> * Output from "dpdk_nic_bind.py --status"? >>> >>> Jay >>> >> >> >