From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk0-f42.google.com (mail-vk0-f42.google.com [209.85.213.42]) by dpdk.org (Postfix) with ESMTP id 092CA2946 for ; Thu, 7 Jul 2016 14:19:33 +0200 (CEST) Received: by mail-vk0-f42.google.com with SMTP id d67so17546145vkh.1 for ; Thu, 07 Jul 2016 05:19:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infinite-io.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=V/fLS9Q5v+W/bWJ79nlWiGgdraz8evesrgvFCWXJApA=; b=dQBNa8VaHMh+9TRQyOAg9Q0Ngh2ytFqyi6o14ZiZBgW9QgsQxDh4FWYIf5rj/I4NGX dczSGQQfAck6pTSzjbe2AbD9h5nO0Fp3DpZBogjv04j8tlb7pIWsbhlJqfa2wRq73/kl 9ULCzbf41YxWdEPReA491NurW1ZbKu1OktR+etXb9Q9qsHkNkqhU4jl1JroiWK9Au2dB qTaRYZhGpXrq1faOKYW4XEkDFXDkSC8pADnAj0IQbT/iYMm6oMFOiv68+yoWC8ul69/+ VOH7lPfkRQyv5nTzepCn88BWj6u2xCc8MPEskMWlSWarhp/5WRXPtyoEHiy42IlEDLFN Ud7w== 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=V/fLS9Q5v+W/bWJ79nlWiGgdraz8evesrgvFCWXJApA=; b=YSdWZRi5bFXV0tamGPtR11J4Zji47ncYAOZ5g5jKhjVM1mkcMLH0tebRJ+74LpmmG4 Dmyz5bpf/tfxU6brMjB6B4fFX2S/sTbAO+66ZZQEA/HODDAJZfQPC/cpxIHsn6E/gScm B8d0S0AEjMuDZ1RQ+HqPOcqffECZcH2USpyJoXc+qfS8SvQxIeCZYJ8i3K5U0tY+5HCO m+2r2ivD5vEE31ql5WzLWoOm+7xRHVuR1CFBPFIXPqoiZ5XmR0CJBJ45TiKcwvMN7gH/ Oua5FTYL2QJIllQBZ9F92avlFcbzfElMvoOCDBh9fAz7+a0ajmW5jzJLPl2pud++CM6C nFlA== X-Gm-Message-State: ALyK8tKVCfaXwRqUVqkWnRE/2IaPCY3Xe/29TyBKoepTawft8aM+O2wbkyjCywWIXzPNUfIBeqDTD8NPVfNtdg== X-Received: by 10.159.36.120 with SMTP id 111mr4593978uaq.106.1467893972503; Thu, 07 Jul 2016 05:19:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.4.2 with HTTP; Thu, 7 Jul 2016 05:19:31 -0700 (PDT) In-Reply-To: References: From: Jay Rolette Date: Thu, 7 Jul 2016 07:19:31 -0500 Message-ID: To: Bill Bonaparte 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: Thu, 07 Jul 2016 12:19:33 -0000 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_u= io > unused=3D > 0000:01:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=3Digb_u= io > 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 >> > >