From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.sandvine.com (Mail1.sandvine.com [64.7.137.134]) by dpdk.org (Postfix) with ESMTP id E3CC891B8 for ; Mon, 4 Jan 2016 22:49:37 +0100 (CET) Received: from WTL-EXCHP-1.sandvine.com ([fe80::ac6b:cc1e:f2ff:93aa]) by wtl-exchp-2.sandvine.com ([fe80::68ac:f071:19ff:3455%19]) with mapi id 14.03.0195.001; Mon, 4 Jan 2016 16:49:40 -0500 From: Tom Crugnale To: "dev@dpdk.org" Thread-Topic: vmxnet3 pmd stats counters reset after rte_eth_dev_start() is called Thread-Index: AdFHNCh7kFi0zRzNQvyJYQYLThXrMA== Date: Mon, 4 Jan 2016 21:49:36 +0000 Message-ID: <9689034CEF26614CAB4B447EEAAF98E918266E3D@wtl-exchp-1.sandvine.com> Accept-Language: en-CA, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.200.64] x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] vmxnet3 pmd stats counters reset after rte_eth_dev_start() is called 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: Mon, 04 Jan 2016 21:49:38 -0000 Hi All, I am seeing an issue where the stats counters for vmxnet3 interfaces are re= set to 0 after rte_eth_dev_start() is called, making it difficult to track = statistics over a period of time where interfaces could be disabled and re-= enabled. There is a memset in the code that clears the txq/rxq stats counters to 0 e= ach time an interface is started from the stopped state. However, even wit= h this code removed, I still see the issue happening. I believe there is s= omething on the host side that is resetting these counters, since they come= from shared memory. Does anyone know what causes the reset, and if there is a way to prevent it= ? I could work around the issue by caching a snapshot of the last statisti= cs before calling rte_eth_dev_start() and then just using that as a baselin= e for accumulation going forward, but I don't think this behaviour exists f= or all other NIC types, so I would have to specialize on the vmxnet3 case. Thanks, Tom