DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kyle Larose <eomereadig@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
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
Date: Wed, 4 Nov 2015 08:13:52 -0500	[thread overview]
Message-ID: <CAMFWN9m1u5pwVSU8OaSRx2gBk2n7xB7u-cDg4qYyyJF8-auojg@mail.gmail.com> (raw)
In-Reply-To: <20151103152850.3e23f639@xeon-e3>

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.

      reply	other threads:[~2015-11-04 13:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03  6:25 최익성
2015-11-03 14:11 ` Wiles, Keith
2015-11-03 14:30   ` Van Haaren, Harry
2015-11-03 14:33     ` Wiles, Keith
2015-11-03 15:59       ` Polehn, Mike A
2015-11-03 19:00         ` Wiles, Keith
2015-11-03 21:55           ` Polehn, Mike A
2015-11-04  1:45         ` 최익성
2015-11-04 14:21           ` Polehn, Mike A
2015-11-04 23:58             ` 최익성
2015-11-03 22:05     ` Stephen Hemminger
2015-11-03 22:18       ` Kyle Larose
2015-11-03 23:28         ` Stephen Hemminger
2015-11-04 13:13           ` Kyle Larose [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMFWN9m1u5pwVSU8OaSRx2gBk2n7xB7u-cDg4qYyyJF8-auojg@mail.gmail.com \
    --to=eomereadig@gmail.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).