DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Rasesh Mody <rasesh.mody@qlogic.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Dept-EngDPDKDev@qlogic.com" <Dept-EngDPDKDev@qlogic.com>
Subject: Re: [dpdk-dev] [PATCH 6/9] qede: add support for xstats
Date: Mon, 9 May 2016 17:56:54 +0000	[thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA6128E0B16@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1462595421-22505-7-git-send-email-rasesh.mody@qlogic.com>

Hi Rasesh,

Some comments about xstats strings below, please refer to the docs here:
http://dpdk.org/doc/guides/prog_guide/poll_mode_drv.html#extended-statistics-api
Due to my familiarity with ixgbe, I will use it as an example: other PMDs should
be identical. 

I understand these may seem trivial and pointless changes, but ensuring the xstats strings are consistent is vital for apps to find the metadata contained.

Regards, -Harry

> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Rasesh Mody
> Subject: [dpdk-dev] [PATCH 6/9] qede: add support for xstats
> 
> This patch adds support for extended statistics for QEDE PMD.
> 	
> +static const struct rte_eth_xstats qede_eth_stats[] = {
> +	{"no_buff_discards",
> +		offsetof(struct ecore_eth_stats, no_buff_discards)},

Is provided by ethdev as rx_mbuf_allocation_errors
http://dpdk.org/browse/dpdk/tree/lib/librte_ether/rte_ethdev.c#n93

> +	{"packet_too_big_discard",
> +		offsetof(struct ecore_eth_stats, packet_too_big_discard)},

Is this not the same as rx_oversize below? It reads like it is - perhaps try be more descriptive (provide a direction, and differentiate it from the counter below) 

> +	{"ttl0_discard", offsetof(struct ecore_eth_stats, ttl0_discard)},

This needs a direction, "rx", I suggest "rx_ttl_zero_dropped" 

> +	{"rx_ucast_bytes", offsetof(struct ecore_eth_stats, rx_ucast_bytes)},
> +	{"rx_mcast_bytes", offsetof(struct ecore_eth_stats, rx_mcast_bytes)},
> +	{"rx_bcast_bytes", offsetof(struct ecore_eth_stats, rx_bcast_bytes)},
> +	{"rx_ucast_pkts", offsetof(struct ecore_eth_stats, rx_ucast_pkts)},
> +	{"rx_mcast_pkts", offsetof(struct ecore_eth_stats, rx_mcast_pkts)},
> +	{"rx_bcast_pkts", offsetof(struct ecore_eth_stats, rx_bcast_pkts)},

expand these names - unicast, packets. Otherwise formatting is good.

> +	{"mftag_filter_discards",
> +		offsetof(struct ecore_eth_stats, mftag_filter_discards)},
> +	{"mac_filter_discards",
> +		offsetof(struct ecore_eth_stats, mac_filter_discards)},

Direction, "mftag"?

> +	{"tx_ucast_bytes", offsetof(struct ecore_eth_stats, tx_ucast_bytes)},
> +	{"tx_mcast_bytes", offsetof(struct ecore_eth_stats, tx_mcast_bytes)},
> +	{"tx_bcast_bytes", offsetof(struct ecore_eth_stats, tx_bcast_bytes)},
> +	{"tx_ucast_pkts", offsetof(struct ecore_eth_stats, tx_ucast_pkts)},
> +	{"tx_mcast_pkts", offsetof(struct ecore_eth_stats, tx_mcast_pkts)},
> +	{"tx_bcast_pkts", offsetof(struct ecore_eth_stats, tx_bcast_pkts)},

Same as RX (expand to unicast etc, packets)

> +	{"tx_err_drop_pkts",
> +		offsetof(struct ecore_eth_stats, tx_err_drop_pkts)},
> +	{"tpa_coalesced_pkts",
> +		offsetof(struct ecore_eth_stats, tpa_coalesced_pkts)},
> +	{"tpa_coalesced_events",
> +		offsetof(struct ecore_eth_stats, tpa_coalesced_events)},
> +	{"tpa_aborts_num", offsetof(struct ecore_eth_stats, tpa_aborts_num)},
> +	{"tpa_not_coalesced_pkts",
> +		offsetof(struct ecore_eth_stats, tpa_not_coalesced_pkts)},
> +	{"tpa_coalesced_bytes",
> +		offsetof(struct ecore_eth_stats, tpa_coalesced_bytes)},

"tpa" should be human-readable, and these need a direction (unless this counter explicitly has no affinity to rx/tx)

> +	{"rx_64_byte_packets",
> +		offsetof(struct ecore_eth_stats, rx_64_byte_packets)},
<<until>>
> +	{"rx_9217_to_16383_byte_packets", offsetof(struct ecore_eth_stats,
> +						rx_9217_to_16383_byte_packets)},

Formatting not consistent, see docs linked at top.		

> +	{"rx_mac_crtl_frames",
> +		offsetof(struct ecore_eth_stats, rx_mac_crtl_frames)},

and 

> +	{"rx_prio_flow_ctrl_frames",
> +		offsetof(struct ecore_eth_stats, rx_pfc_frames)},

Expand crtl

> +	{"rx_oversize_packets",
> +		offsetof(struct ecore_eth_stats, rx_oversize_packets)},

Does this packet get received properly? If so, packets is the right counter. Otherwise this should be errors:
http://dpdk.org/browse/dpdk/tree/drivers/net/ixgbe/ixgbe_ethdev.c#n617

> +	{"rx_jabbers", offsetof(struct ecore_eth_stats, rx_jabbers)},

rx_jabber_errors

> +	{"rx_undersize_packets",
> +		offsetof(struct ecore_eth_stats, rx_undersize_packets)},

Same as oversize.

> +	{"rx_fragments", offsetof(struct ecore_eth_stats, rx_fragments)},

rx_fragment_packets?
http://dpdk.org/browse/dpdk/tree/drivers/net/ixgbe/ixgbe_ethdev.c#n615

> +	{"tx_64_byte_packets",
> +		offsetof(struct ecore_eth_stats, tx_64_byte_packets)},

Same as RX size comment.

  reply	other threads:[~2016-05-09 17:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-07  4:30 [dpdk-dev] [PATCH 0/9] qede: update qede PMD to 1.1.0.1 Rasesh Mody
2016-05-07  4:30 ` [dpdk-dev] [PATCH 1/9] qede: update hash config Rasesh Mody
2016-05-07  4:30 ` [dpdk-dev] [PATCH 2/9] qede: get hash configuration Rasesh Mody
2016-05-07  4:30 ` [dpdk-dev] [PATCH 3/9] qede: rss redirection table update Rasesh Mody
2016-05-07  4:30 ` [dpdk-dev] [PATCH 4/9] qede: rss redirection table query Rasesh Mody
2016-05-07  4:30 ` [dpdk-dev] [PATCH 5/9] qede: set mtu Rasesh Mody
2016-05-07  4:30 ` [dpdk-dev] [PATCH 6/9] qede: add support for xstats Rasesh Mody
2016-05-09 17:56   ` Van Haaren, Harry [this message]
2016-05-07  4:30 ` [dpdk-dev] [PATCH 7/9] qede: add 100g mode support Rasesh Mody
2016-06-07 11:09   ` Bruce Richardson
2016-05-07  4:30 ` [dpdk-dev] [PATCH 8/9] qede: enable vf-vf traffic with unmatched dest addr Rasesh Mody
2016-06-07 12:37   ` Bruce Richardson
2016-05-07  4:30 ` [dpdk-dev] [PATCH 9/9] qede: update version to 8.7.9.0_1.1.0.1 Rasesh Mody
2016-05-23  0:56 ` [dpdk-dev] [PATCH 0/9] qede: update qede PMD to 1.1.0.1 Rasesh Mody
2016-06-07 12:47   ` Bruce Richardson
2016-06-07 18:26     ` Rasesh Mody

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=E923DB57A917B54B9182A2E928D00FA6128E0B16@IRSMSX102.ger.corp.intel.com \
    --to=harry.van.haaren@intel.com \
    --cc=Dept-EngDPDKDev@qlogic.com \
    --cc=dev@dpdk.org \
    --cc=rasesh.mody@qlogic.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).