From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ido Goshen <ido@cgstowernetworks.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/1] net/pcap: imissed stats support
Date: Thu, 28 Jan 2021 18:10:10 +0000 [thread overview]
Message-ID: <c6be02ad-5eae-505b-a849-3b20c622542e@intel.com> (raw)
In-Reply-To: <20210125175836.87200-1-ido@cgstowernetworks.com>
On 1/25/2021 5:58 PM, Ido Goshen wrote:
> Signed-off-by: Ido Goshen <ido@cgstowernetworks.com>
> ---
> drivers/net/pcap/rte_eth_pcap.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/drivers/net/pcap/rte_eth_pcap.c b/drivers/net/pcap/rte_eth_pcap.c
> index a32b1f3f3..83e208514 100644
> --- a/drivers/net/pcap/rte_eth_pcap.c
> +++ b/drivers/net/pcap/rte_eth_pcap.c
> @@ -58,6 +58,7 @@ struct queue_stat {
> volatile unsigned long pkts;
> volatile unsigned long bytes;
> volatile unsigned long err_pkts;
> + volatile unsigned long missed_reset;
> };
>
> struct pcap_rx_queue {
> @@ -680,11 +681,23 @@ eth_dev_info(struct rte_eth_dev *dev,
> return 0;
> }
>
> +static unsigned long
> +eth_stats_get_pcap_missed(struct rte_eth_dev *dev, unsigned int qid)
> +{
> + const struct pmd_process_private *pp = dev->process_private;
> + pcap_t *pcap = pp->rx_pcap[qid];
> + struct pcap_stat stat;
> + if (pcap_stats(pcap, &stat) != 0)
If the stats requested after "port stop" this will crash, since "port stop" will
close the pcap.
Although unlikely that stats will be called after "port stop", still it may be
and better to put a protection here.
> + return 0;
> + return stat.ps_drop;
> +}
> +
> static int
> eth_stats_get(struct rte_eth_dev *dev, struct rte_eth_stats *stats)
> {
> unsigned int i;
> unsigned long rx_packets_total = 0, rx_bytes_total = 0;
> + unsigned long rx_missed_total = 0;
> unsigned long tx_packets_total = 0, tx_bytes_total = 0;
> unsigned long tx_packets_err_total = 0;
> const struct pmd_internals *internal = dev->data->dev_private;
> @@ -695,6 +708,10 @@ eth_stats_get(struct rte_eth_dev *dev, struct rte_eth_stats *stats)
> stats->q_ibytes[i] = internal->rx_queue[i].rx_stat.bytes;
> rx_packets_total += stats->q_ipackets[i];
> rx_bytes_total += stats->q_ibytes[i];
> + unsigned long rx_missed = eth_stats_get_pcap_missed(dev, i);
> + if (rx_missed)
> + rx_missed_total = rx_missed -
> + internal->rx_queue[i].rx_stat.missed_reset;
rx_missed_total +=
After a "port stop" & "port start" the 'stat.ps_drop' will be reset, if stats
cleared before, because of stored 'missed_reset', possible to see very big (and
wrong) stat values.
Better to clear the 'missed_reset' on port stop.
> }
>
> for (i = 0; i < RTE_ETHDEV_QUEUE_STAT_CNTRS &&
> @@ -708,6 +725,7 @@ eth_stats_get(struct rte_eth_dev *dev, struct rte_eth_stats *stats)
>
> stats->ipackets = rx_packets_total;
> stats->ibytes = rx_bytes_total;
> + stats->imissed = rx_missed_total;
> stats->opackets = tx_packets_total;
> stats->obytes = tx_bytes_total;
> stats->oerrors = tx_packets_err_total;
> @@ -724,6 +742,8 @@ eth_stats_reset(struct rte_eth_dev *dev)
> for (i = 0; i < dev->data->nb_rx_queues; i++) {
> internal->rx_queue[i].rx_stat.pkts = 0;
> internal->rx_queue[i].rx_stat.bytes = 0;
> + internal->rx_queue[i].rx_stat.missed_reset =
> + eth_stats_get_pcap_missed(dev, i);
> }
>
> for (i = 0; i < dev->data->nb_tx_queues; i++) {
>
next prev parent reply other threads:[~2021-01-28 18:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 17:58 Ido Goshen
2021-01-28 18:10 ` Ferruh Yigit [this message]
2021-02-01 8:30 ` [dpdk-dev] [PATCH v2] " Ido Goshen
2021-02-01 11:48 ` Ferruh Yigit
2021-02-01 14:02 ` Ido Goshen
2021-02-01 16:21 ` Ferruh Yigit
2021-02-03 23:07 ` [dpdk-dev] [PATCH v3 1/1] " Ido Goshen
2021-02-04 0:13 ` Ferruh Yigit
2021-02-04 7:56 ` Ido Goshen
2021-02-04 9:26 ` Ferruh Yigit
2021-02-04 10:02 ` Ido Goshen
2021-02-04 10:27 ` Ferruh Yigit
2021-02-04 10:33 ` [dpdk-dev] [PATCH v4 " Ido Goshen
2021-02-04 18:31 ` Ferruh Yigit
2021-02-22 18:13 ` Ferruh Yigit
2021-01-28 18:20 ` [dpdk-dev] [PATCH " Ferruh Yigit
2021-02-01 8:53 ` Ido Goshen
2021-02-01 9:25 ` Ferruh Yigit
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=c6be02ad-5eae-505b-a849-3b20c622542e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=ido@cgstowernetworks.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).