DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@mellanox.com>
To: Mohsin Shaikh <mohsinshaikh@niometrics.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	Alexander Kozyrev <akozyrev@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: use open/read/close for reading ib stat
Date: Tue, 14 Apr 2020 14:17:06 +0000	[thread overview]
Message-ID: <AM0PR05MB6707D013B36D7208EA20DB00C2DA0@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1586464626-12958-1-git-send-email-mohsinshaikh@niometrics.com>

Hi,


> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Mohsin Shaikh
> Sent: Thursday, April 9, 2020 11:37 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Alexander Kozyrev <akozyrev@mellanox.com>;
> Mohsin Shaikh <mohsinshaikh@niometrics.com>
> Subject: [dpdk-dev] [PATCH] net/mlx5: use open/read/close for reading ib
> stat
> 
> fgets(3)/fread(3)/fscanf(3) etc. use mmap(2)/munmap(2) which leads
> to TLB shootdown interrupts to all dpdk app cores including RX cores.
> This can cause packet drops. Use read(2)/write(2) instead.
> 
> Bugzilla ID: 440
> Cc: stable@dpdk.org
> 
> Signed-off-by: Mohsin Shaikh <mohsinshaikh@niometrics.com>
> ---
>  drivers/net/mlx5/mlx5_stats.c | 21 +++++++++++++--------
>  1 file changed, 13 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/net/mlx5/mlx5_stats.c b/drivers/net/mlx5/mlx5_stats.c
> index 7603502..b2c09d8 100644
> --- a/drivers/net/mlx5/mlx5_stats.c
> +++ b/drivers/net/mlx5/mlx5_stats.c
> @@ -3,11 +3,13 @@
>   * Copyright 2015 Mellanox Technologies, Ltd
>   */
> 
> +#include <fcntl.h>
>  #include <inttypes.h>
>  #include <linux/sockios.h>
>  #include <linux/ethtool.h>
>  #include <stdint.h>
>  #include <stdio.h>
> +#include <unistd.h>
> 
>  #include <rte_ethdev_driver.h>
>  #include <rte_common.h>
> @@ -142,20 +144,23 @@
>  static inline void
>  mlx5_read_ib_stat(struct mlx5_priv *priv, const char *ctr_name, uint64_t
> *stat)
>  {
> -	FILE *file;
> +	int fd;
> +
>  	if (priv->sh) {
>  		MKSTR(path, "%s/ports/%d/hw_counters/%s",
>  			  priv->sh->ibdev_path,
>  			  priv->ibv_port,
>  			  ctr_name);
> -
> -		file = fopen(path, "rb");
> -		if (file) {
> -			int n = fscanf(file, "%" SCNu64, stat);
> -
> -			fclose(file);
> -			if (n == 1)
> +		fd = open(path, O_RDONLY);
> +		if (fd != -1) {
> +			char buf[21] = {'\0'};
> +			ssize_t n = read(fd, buf, sizeof(buf));
> +
> +			close(fd);
> +			if (n != -1) {
> +				*stat = strtoull(buf, NULL, 10);
>  				return;
> +			}
>  		}
>  	}
>  	*stat = 0;
> --
> 1.8.3.1


Patch rebased and applied to next-net-mlx,

Kindest regards
Raslan Darawsheh

      parent reply	other threads:[~2020-04-14 14:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 20:37 Mohsin Shaikh
2020-04-09 22:20 ` Alexander Kozyrev
2020-04-13 10:48   ` Slava Ovsiienko
2020-04-14 14:17 ` Raslan Darawsheh [this message]

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=AM0PR05MB6707D013B36D7208EA20DB00C2DA0@AM0PR05MB6707.eurprd05.prod.outlook.com \
    --to=rasland@mellanox.com \
    --cc=akozyrev@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=mohsinshaikh@niometrics.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@mellanox.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).