From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eomereadig@gmail.com>
Received: from mail-oi0-f51.google.com (mail-oi0-f51.google.com
 [209.85.218.51]) by dpdk.org (Postfix) with ESMTP id A91DF378E
 for <dev@dpdk.org>; Wed,  4 Nov 2015 14:13:52 +0100 (CET)
Received: by oies66 with SMTP id s66so27465677oie.1
 for <dev@dpdk.org>; Wed, 04 Nov 2015 05:13:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=oFAEDv1dCYa2mStWymhSV92Qvk2WFGj6dQGV37iPQ5k=;
 b=geoMURgxUXYkQpGA7qcak46eO67wSeJ40gf0uWY1HYxbWEyIlH3AVo13X8N7/VDc83
 Y605uZfMaHiZiI0O1Ms4FCoKvAaecjM20VFPQotqmRrwkv5JnJOYK0Ic7N8/guIXCtpw
 TQzvUnZ+RiLnYPmwJLiVtoeOW5rnL0e+sND0bOdNWUSkQATRNwpyfrafQSRGGluMKqba
 qe7mjlHwmMz3Ut9cdhBMhPld6Oa2cVp2q32E4FPnMBEY37WhG6ymSbnzgOg5n215IAP7
 GFFpDUl0+qRznEJf2oZrzfL8Vyqjk4Pnw0UcyrDp7PAmrKl4ug7JJg+8EMglb/1EhPO5
 ZuiQ==
MIME-Version: 1.0
X-Received: by 10.202.198.213 with SMTP id w204mr782438oif.72.1446642832194;
 Wed, 04 Nov 2015 05:13:52 -0800 (PST)
Received: by 10.76.68.202 with HTTP; Wed, 4 Nov 2015 05:13:52 -0800 (PST)
In-Reply-To: <20151103152850.3e23f639@xeon-e3>
References: <c730b82a7e135bd8a1bb98bf514b338@cweb15.nm.nhnsystem.com>
 <514E811C-1D85-4BB7-AA9C-C5D2B2ED6043@intel.com>
 <E923DB57A917B54B9182A2E928D00FA61282AF06@IRSMSX102.ger.corp.intel.com>
 <20151103140531.677eee6d@xeon-e3>
 <CAMFWN9=3m0u9TC5TP3v1yCn-7kNLqWwf8-eCCtONL5vygSwZxA@mail.gmail.com>
 <20151103152850.3e23f639@xeon-e3>
Date: Wed, 4 Nov 2015 08:13:52 -0500
Message-ID: <CAMFWN9m1u5pwVSU8OaSRx2gBk2n7xB7u-cDg4qYyyJF8-auojg@mail.gmail.com>
From: Kyle Larose <eomereadig@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Content-Type: text/plain; charset=UTF-8
Cc: "dev@dpdk.org" <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 <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Nov 2015 13:13:53 -0000

On Tue, Nov 3, 2015 at 6:28 PM, Stephen Hemminger
<stephen@networkplumber.org> wrote:

>
> No. configuration is the enemy of usability.
> Why does DPDK have to behave differently than BSD and Linux, what possible
> value could this be to the end user?

I honestly can't think of any good reasons for why a user would need
this. I figured it'd be worth asking to see if anyone thought it would
be. I guess not. :P

I'm still concerned about NICs which may not support disabling CRC
counting, but there's no need to clutter the ethdev API with an extra
attribute without a clear example of such a NIC.