From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f41.google.com (mail-pa0-f41.google.com [209.85.220.41]) by dpdk.org (Postfix) with ESMTP id 5DD0420F for ; Wed, 1 Apr 2015 20:36:00 +0200 (CEST) Received: by pacgg7 with SMTP id gg7so59761743pac.0 for ; Wed, 01 Apr 2015 11:35:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=VE0F0PiuCIUSNP/wVPwndyIqd/NWRkeY+YAUNKwNv60=; b=VSVE00x0ymsCaMQpigw0nstgC/IAOyi27A2BVm6Zn/3tFsmKdrOelJdQwuLSDAULOX dHu/9Anj4C+sCqWWLxWxzIcArcfz13BVY7oVraMRA4qvbBu2lyMJKXOBtCFPiUUauw+c ZarNqJ22sjS+nAOhHiOaN0gZPloKNabI1RzwPCtaZAs7CcXCH48MZ6aFkc10NA0d1lzm Rmo/pLu5i4uFYBx128637CtBU3MJAEM1M4af3AGD5pgShjC1B6D04WvOp2NUl6YwSkDI aHF28vXZxs+XF7NCZhx15joMFzDguzCKuFS7B3Daa8DdhKDUll9o1Ql134KuJRJ4EzuT iRwg== X-Gm-Message-State: ALoCoQlA/hOGZMTyV1iFHFrPzUFOcB8DOGpo9swk3owMQPzQmTQitdn/gc+336RGiRn4rzZGOGBs X-Received: by 10.68.170.3 with SMTP id ai3mr28468440pbc.19.1427913358391; Wed, 01 Apr 2015 11:35:58 -0700 (PDT) Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net. [50.53.82.155]) by mx.google.com with ESMTPSA id in4sm2816759pbd.40.2015.04.01.11.35.57 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Apr 2015 11:35:58 -0700 (PDT) Date: Wed, 1 Apr 2015 11:36:03 -0700 From: Stephen Hemminger To: Thomas Monjalon Message-ID: <20150401113603.3591ad48@urahara> In-Reply-To: References: <2601191342CEEE43887BDE71AB977258214074F6@irsmsx105.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" , Stephen Hemminger Subject: Re: [dpdk-dev] [PATCH] ixgbe: do not include CRC in Tx byte count 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: Wed, 01 Apr 2015 18:36:00 -0000 On Wed, 1 Apr 2015 07:45:02 +0000 Thomas Monjalon wrote: > 2015-03-24 23:54, Ananyev, Konstantin: > > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > > > On Mon, 23 Mar 2015 16:45:44 +0000 > > > "Ananyev, Konstantin" wrote: > > > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of stephen@networkplumber.org > > > > > From: Stephen Hemminger > > > > > > > > > > The ixgbe driver was including CRC in the transmit packet byte > > > > > count, but not for packets received. > > > > > This was notice when forwarding and > > > > > the number of bytes received was greater than the number of bytes transmitted > > > > > for the same number of packets. Make the driver behave like other > > > > > virtual devices and not include CRC in byte count. Use the same queue > > > > > counters already computed and used for Rx. > > > > > > > > About RX side stats - as I remember it depends to what value hw_stip_crc is set at configure(). > > > > If hw_stip_crc==1, then, yes CRC bytes are not included into QBRC value. > > > > I If hw_stip_crc==0, then CRC bytes are included into QBRC. > > > > > > That is an additional bug! > > > * CRC should never be included in the byte count. > > > This is not how Linux or other drivers report byte count. > > > > I don't have any strong opinion here... > > For me any method (with or without CRC) of counting bytes are ok, as long as this method is identical across all PMDs we support. > > Which makes we wonder, what approach other PMDs use? > > > > > > > > * the byte count must be symmetrical Rx == Tx > > > > > > The Brocade router always set strip_crc to 1. So did not see the additional bug > > > of CRC being included in byte count. > > > > Are you going to submit v2, to make Rx==Tx for both cases? > > Any conclusion? > Without update, this patch is going to be dropped. I was hoping Intel would maintain their drivers and fix the issue. Don't have resources to do it across all configurations and hardware, my bet is that this is broken on i40e, igb, e1000 as well.