DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Qiming Chen <chenqiming_huawei@163.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4] net/pcap: improve rx statistics
Date: Thu, 9 Sep 2021 09:05:41 +0100	[thread overview]
Message-ID: <e5bfbedb-8e04-929f-5bcd-572f867e3e5b@intel.com> (raw)
In-Reply-To: <20210909041658.10123-1-chenqiming_huawei@163.com>

On 9/9/2021 5:16 AM, Qiming Chen wrote:
> In the receiving direction, if alloc mbuf or jumbo process failed, there
> is no err_pkts count, which makes it difficult to locate the problem.
> Because alloc mbuf failed, the rx_nombuf field is counted.
> 

Please fix './devtools/check-git-log.sh' warnings.

> Signed-off-by: Qiming Chen <chenqiming_huawei@163.com>
> ---
> v2:
>   Clear coding style issues.
> v3:
>   1) Send direction does not release mbuf.
>   2) Failed to alloc mbuf is counted to the rx_nombuf field.
> v4:
>   Add rx_nombuf field.

<...>

> @@ -297,8 +298,10 @@ eth_pcap_rx(void *queue, struct rte_mbuf **bufs, uint16_t nb_pkts)
>  			break;
>  
>  		mbuf = rte_pktmbuf_alloc(pcap_q->mb_pool);
> -		if (unlikely(mbuf == NULL))
> -			break;
> +		if (unlikely(mbuf == NULL)) {
> +			pcap_q->rx_stat.rx_nombuf++;
> +			continue;

Not sure to update to 'continue' here. I guess both works but if allocating an
mbuf failed, keeping continue to the loop may cause more mbuf allocation
failure, 'break' may give more time to have mbufs available.

Also the patch is related to adding stats, so lets not update the behavior in
this patch.

> +		}
>  
>  		if (header.caplen <= rte_pktmbuf_tailroom(mbuf)) {
>  			/* pcap packet will fit in the mbuf, can copy it */
> @@ -311,6 +314,7 @@ eth_pcap_rx(void *queue, struct rte_mbuf **bufs, uint16_t nb_pkts)
>  						       mbuf,
>  						       packet,
>  						       header.caplen) == -1)) {
> +				pcap_q->rx_stat.rx_nombuf++;

This one should update 'err_pkts'.

  reply	other threads:[~2021-09-09  8:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26  3:16 [dpdk-dev] [PATCH] net/pcap: improve rxtx statistics Qiming Chen
2021-08-26  3:23 ` [dpdk-dev] [PATCH v2] " Qiming Chen
2021-09-08 12:29   ` Ferruh Yigit
2021-09-09  2:45   ` [dpdk-dev] [PATCH v3] net/pcap: improve rx statistics Qiming Chen
2021-09-09  3:29     ` Stephen Hemminger
2021-09-09 10:20       ` Ferruh Yigit
2021-09-09  4:16     ` [dpdk-dev] [PATCH v4] " Qiming Chen
2021-09-09  8:05       ` Ferruh Yigit [this message]
2021-09-09  8:23       ` [dpdk-dev] [PATCH v5] " Qiming Chen
2021-09-09 10:20         ` Ferruh Yigit
2021-09-09 12:28         ` [dpdk-dev] [PATCH v6] " Qiming Chen
2021-09-09 14:45           ` 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=e5bfbedb-8e04-929f-5bcd-572f867e3e5b@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=chenqiming_huawei@163.com \
    --cc=dev@dpdk.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).