From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by dpdk.org (Postfix) with ESMTP id 456D18E86 for ; Tue, 3 Nov 2015 23:05:21 +0100 (CET) Received: by pacdm15 with SMTP id dm15so5820541pac.3 for ; Tue, 03 Nov 2015 14:05:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber_org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=8v2IVxnfXo6MYzO/QIueTMLKaI+HX/bA/hQmnkKt334=; b=nS+Coz6aO9FWOb/BpDbM9qiAh0n4cP4S0p39WFcj9b771YXN7L6TwLKa5Fff1lt3HK UOYsmKuIIj9Rmrc175qIzCcG0ztVEYgVM9CCSy5qDIIsVrtS+9mxBsdO45Ux/jZjUKQy LjTLbem3UN5PC/CG7gMKZqCoWiRkZ73n95QCpHcKYYhu1z9FDpce8wtrAgNb3WZv6WeR NUewnbEbMxgtRxYL09FZS7RggUjjeqVkcOnvRoJXCT0gLxQEZT5M11qcHsvQ86DBknyl O2qQWQfgmaG6yuUMMw9jbdN3M6jEptjyWuJkoUXUlAFEyO/qs6AB9OK5imy4wYtJoyzc zptw== 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=8v2IVxnfXo6MYzO/QIueTMLKaI+HX/bA/hQmnkKt334=; b=cjEi4L1+RgTy8sGeXxprB0zhAFcJH2hRV56UMEM2QUYgRceGK13yTg7gJG/vvcSboL WDT43QaAjmC7d1lA22DDL3pvVU6Qi8KbgujFBPFZwYu9OJih8qJIziW3ROL8a5ME3B0x 21JUFTY5Zwjx04EFc94j75MEvu2L4awfBGA8M9UDHiBNW6SCCWhYx3VRkPmUgNukaycH KtK2oFtP8uhD6DXdlveXDicOlr9UuBen66zkV7BeEAYWQ7Hbxj0bnLKT0J3dHteICWQ4 HxrHMdKI/Cba6st2cQmqefxWpOMkS7vSf/2FZbvZVPecoKQTPfEgOYhO7CHDrotlNZzI nfeg== X-Gm-Message-State: ALoCoQm/CpsmX53IfYYLWjuomsC4h7EjjRk79dLRNen3+7UCp7ZtYV2Mvi+wfC5vcDf7y5f2NR6x X-Received: by 10.66.255.66 with SMTP id ao2mr35921753pad.97.1446588320607; Tue, 03 Nov 2015 14:05:20 -0800 (PST) Received: from xeon-e3 (static-50-53-82-155.bvtn.or.frontiernet.net. [50.53.82.155]) by smtp.gmail.com with ESMTPSA id wq1sm31273282pbc.49.2015.11.03.14.05.20 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Nov 2015 14:05:20 -0800 (PST) Date: Tue, 3 Nov 2015 14:05:31 -0800 From: Stephen Hemminger To: "Van Haaren, Harry" Message-ID: <20151103140531.677eee6d@xeon-e3> In-Reply-To: References: <514E811C-1D85-4BB7-AA9C-C5D2B2ED6043@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] How can I calculate/estimate pps(packet per seocond) and bps(bit per second) in DPDK pktg 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, 03 Nov 2015 22:05:22 -0000 On Tue, 3 Nov 2015 14:30:41 +0000 "Van Haaren, Harry" wrote: > Hi Keith, > > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wiles, Keith > > > Hmm, I just noticed I did not include the FCS bytes. Does the NIC include FCS bytes in the > > counters? Need to verify that one and if not then it becomes a bit more complex. > > The Intel NICs count packet sizes inclusive of CRC / FCS, from eg the ixgbe/82599 datasheet: > "This register includes bytes received in a packet from the field through the field, inclusively." > > -Harry IMHO this is a bug. Other drivers don't include the CRC, and the Intel driver only includes CRC in count for one direction, and depends on value of stripping flag. I sent a patch to fix this because our customers didn't like it when Rx != Tx bytes but there was somebody who liked including CRC. It really is a Cisco versus the world thing. Juniper/Linux/BSD all do NOT include CRC in counters and therefore that is what should be done.