From: Stephen Hemminger <stephen@networkplumber.org>
To: Maryam Tahhan <maryam.tahhan@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/4] ixgbe: expose extended error statistics
Date: Tue, 9 Jun 2015 17:51:07 -0700 [thread overview]
Message-ID: <20150609175107.2c6bc94d@urahara> (raw)
In-Reply-To: <1433525705-17041-2-git-send-email-maryam.tahhan@intel.com>
On Fri, 5 Jun 2015 18:35:02 +0100
Maryam Tahhan <maryam.tahhan@intel.com> wrote:
> Implement xstats_get() and xstats_reset() in dev_ops for ixgbe to expose
> detailed error statistics to DPDK applications.
>
> Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.com>
Also, the bug where CRC is included in Tx byte count but
not in the Rx byte count has not been addressed.
You seem to have ignored my earlier patch.
next prev parent reply other threads:[~2015-06-10 0:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 17:35 [dpdk-dev] [PATCH 0/4] expose ixgbe extended stats to dpdk apps Maryam Tahhan
2015-06-05 17:35 ` [dpdk-dev] [PATCH 1/4] ixgbe: expose extended error statistics Maryam Tahhan
2015-06-08 13:26 ` Tahhan, Maryam
2015-06-10 0:51 ` Stephen Hemminger [this message]
2015-06-10 14:24 ` Tahhan, Maryam
2015-06-17 12:52 ` Thomas Monjalon
2015-06-05 17:35 ` [dpdk-dev] [PATCH 2/4] ethdev: expose extended error stats Maryam Tahhan
2015-06-17 13:58 ` Thomas Monjalon
2015-06-17 14:47 ` Kyle Larose
2015-06-22 14:12 ` Tahhan, Maryam
2015-06-22 15:12 ` Olivier MATZ
2015-06-22 15:35 ` Tahhan, Maryam
2015-06-05 17:35 ` [dpdk-dev] [PATCH 3/4] testpmd: extend testpmd to show all extended stats Maryam Tahhan
2015-06-05 17:35 ` [dpdk-dev] [PATCH 4/4] app: replace dump_cfg with proc_info Maryam Tahhan
2015-06-05 21:08 ` Thomas Monjalon
2015-06-08 13:45 ` Tahhan, Maryam
2015-06-08 14:22 ` Thomas Monjalon
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=20150609175107.2c6bc94d@urahara \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=maryam.tahhan@intel.com \
/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).