From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Maryam Tahhan <maryam.tahhan@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4 8/8] app: add a new app proc_info
Date: Thu, 09 Jul 2015 03:39:35 +0200 [thread overview]
Message-ID: <3280448.8fAfYn9D23@xps13> (raw)
In-Reply-To: <1436118000-132275-9-git-send-email-maryam.tahhan@intel.com>
2015-07-05 18:40, Maryam Tahhan:
> proc_info displays statistics information including extened stats for
typo: extended
> given DPDK ports and dumps the memory information for DPDK.
>
> Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.com>
> ---
> MAINTAINERS | 4 +
> app/Makefile | 1 +
> app/proc_info/Makefile | 45 +++++
> app/proc_info/main.c | 512 +++++++++++++++++++++++++++++++++++++++++++++++++
> mk/rte.sdktest.mk | 4 +-
> 5 files changed, 564 insertions(+), 2 deletions(-)
A doc would be useful.
> +DIRS-$(CONFIG_RTE_LIBRTE_EAL_LINUXAPP) += proc_info
Why only Linux?
> +# Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
Too old :)
> + if ((!port->rx_queue_stats_mapping_enabled) && (!port->tx_queue_stats_mapping_enabled)) {
> + printf(" RX-packets: %-10"PRIu64" RX-missed: %-10"PRIu64" RX-bytes: "
> + "%-"PRIu64"\n",
> + stats.ipackets, stats.imissed, stats.ibytes);
> + printf(" RX-badcrc: %-10"PRIu64" RX-badlen: %-10"PRIu64" RX-errors: "
> + "%-"PRIu64"\n",
> + stats.ibadcrc, stats.ibadlen, stats.ierrors);
> + printf(" RX-nombuf: %-10"PRIu64"\n",
> + stats.rx_nombuf);
> + printf(" TX-packets: %-10"PRIu64" TX-errors: %-10"PRIu64" TX-bytes: "
> + "%-"PRIu64"\n",
> + stats.opackets, stats.oerrors, stats.obytes);
> + } else {
> + printf(" RX-packets: %10"PRIu64" RX-errors: %10"PRIu64
> + " RX-bytes: %10"PRIu64"\n",
> + stats.ipackets, stats.ierrors, stats.ibytes);
> + printf(" RX-badcrc: %10"PRIu64" RX-badlen: %10"PRIu64
> + " RX-errors: %10"PRIu64"\n",
> + stats.ibadcrc, stats.ibadlen, stats.ierrors);
> + printf(" RX-nombuf: %10"PRIu64"\n",
> + stats.rx_nombuf);
> + printf(" TX-packets: %10"PRIu64" TX-errors: %10"PRIu64
> + " TX-bytes: %10"PRIu64"\n",
> + stats.opackets, stats.oerrors, stats.obytes);
> + }
Why the formatting is different depending of device-specific stats mapping?
> + if (port->rx_queue_stats_mapping_enabled) {
> + printf("\n");
> + for (i = 0; i < RTE_ETHDEV_QUEUE_STAT_CNTRS; i++) {
> + printf(" Stats reg %2d RX-packets: %10"PRIu64
> + " RX-errors: %10"PRIu64
> + " RX-bytes: %10"PRIu64"\n",
> + i, stats.q_ipackets[i], stats.q_errors[i], stats.q_ibytes[i]);
> + }
> + }
Why restricting stats per queue to devices requiring a mapping?
> - $(RTE_OUTPUT)/app/dump_cfg --file-prefix=ring_perf ; \
This should have been removed in previous patch.
next prev parent reply other threads:[~2015-07-09 1:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-05 17:39 [dpdk-dev] [PATCH v4 0/8] Expose IXGBE extended stats to DPDK apps Maryam Tahhan
2015-07-05 17:39 ` [dpdk-dev] [PATCH v4 1/8] ixgbe: move stats register reads to a new function Maryam Tahhan
2015-07-05 17:39 ` [dpdk-dev] [PATCH v4 2/8] ixgbe: add functions to get and reset xstats Maryam Tahhan
2015-07-05 17:39 ` [dpdk-dev] [PATCH v4 3/8] ethdev: expose extended error stats Maryam Tahhan
2015-07-15 9:18 ` Olivier MATZ
2015-07-15 13:14 ` Tahhan, Maryam
2015-07-05 17:39 ` [dpdk-dev] [PATCH v4 4/8] ethdev: remove HW specific stats in stats structs Maryam Tahhan
2015-07-05 17:39 ` [dpdk-dev] [PATCH v4 5/8] ixgbe: add NIC specific stats removed from ethdev Maryam Tahhan
2015-07-05 17:39 ` [dpdk-dev] [PATCH v4 6/8] ixgbe: return more errors in ierrors Maryam Tahhan
2015-07-05 17:39 ` [dpdk-dev] [PATCH v4 7/8] app: remove dump_cfg Maryam Tahhan
2015-07-05 17:40 ` [dpdk-dev] [PATCH v4 8/8] app: add a new app proc_info Maryam Tahhan
2015-07-09 1:39 ` Thomas Monjalon [this message]
2015-07-13 13:30 ` Tahhan, Maryam
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=3280448.8fAfYn9D23@xps13 \
--to=thomas.monjalon@6wind.com \
--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).