DPDK patches and discussions
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@mellanox.com>
To: Moti Haimovsky <motih@mellanox.com>,
	Raslan Darawsheh <rasland@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: retry when link update fails
Date: Wed, 16 Oct 2019 07:42:18 +0000	[thread overview]
Message-ID: <AM4PR05MB326562B2F5645775D19CBAEFD2920@AM4PR05MB3265.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <afbce1987c0f23a2f991a45c3f553c0753bb8d49.1571210479.git.motih@mellanox.com>

> -----Original Message-----
> From: Moti Haimovsky <motih@mellanox.com>
> Sent: Wednesday, October 16, 2019 10:34
> To: Slava Ovsiienko <viacheslavo@mellanox.com>; Raslan Darawsheh
> <rasland@mellanox.com>
> Cc: dev@dpdk.org
> Subject: [PATCH v2] net/mlx5: retry when link update fails
> 
> mlx5_link_update immediately returns when called with no-wait parameter
> and its call for retrieving the link status returns with EAGAIN error.
> This is too harsh on busy systems where a first call fails with EAGAIN from
> time to time.
> This patch adds a (very limited) retry on such cases in order to allow
> retrieving the link status.
> 
> Signed-off-by: Moti Haimovsky <motih@mellanox.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>

> ---
> V2:
> * Code rebase
> ---
>  drivers/net/mlx5/mlx5_defs.h   | 3 +++
>  drivers/net/mlx5/mlx5_ethdev.c | 5 +++--
>  2 files changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/mlx5/mlx5_defs.h b/drivers/net/mlx5/mlx5_defs.h
> index 180122d..248ef3c 100644
> --- a/drivers/net/mlx5/mlx5_defs.h
> +++ b/drivers/net/mlx5/mlx5_defs.h
> @@ -105,6 +105,9 @@
>  /* Timeout in seconds to get a valid link status. */  #define
> MLX5_LINK_STATUS_TIMEOUT 10
> 
> +/* Number of times to retry retrieving the physical link information.
> +*/ #define MLX5_GET_LINK_STATUS_RETRY_COUNT 3
> +
>  /* Maximum number of UAR pages used by a port,
>   * These are the size and mask for an array of mutexes used to synchronize
>   * the access to port's UARs on platforms that do not support 64 bit writes.
> diff --git a/drivers/net/mlx5/mlx5_ethdev.c
> b/drivers/net/mlx5/mlx5_ethdev.c index f2b1752..5f05b2b 100644
> --- a/drivers/net/mlx5/mlx5_ethdev.c
> +++ b/drivers/net/mlx5/mlx5_ethdev.c
> @@ -999,6 +999,7 @@ int mlx5_fw_version_get(struct rte_eth_dev *dev,
> char *fw_ver, size_t fw_size)
>  	int ret;
>  	struct rte_eth_link dev_link;
>  	time_t start_time = time(NULL);
> +	int retry = MLX5_GET_LINK_STATUS_RETRY_COUNT;
> 
>  	do {
>  		ret = mlx5_link_update_unlocked_gs(dev, &dev_link); @@ -
> 1007,7 +1008,7 @@ int mlx5_fw_version_get(struct rte_eth_dev *dev, char
> *fw_ver, size_t fw_size)
>  		if (ret == 0)
>  			break;
>  		/* Handle wait to complete situation. */
> -		if (wait_to_complete && ret == -EAGAIN) {
> +		if ((wait_to_complete || retry) && ret == -EAGAIN) {
>  			if (abs((int)difftime(time(NULL), start_time)) <
>  			    MLX5_LINK_STATUS_TIMEOUT) {
>  				usleep(0);
> @@ -1019,7 +1020,7 @@ int mlx5_fw_version_get(struct rte_eth_dev *dev,
> char *fw_ver, size_t fw_size)
>  		} else if (ret < 0) {
>  			return ret;
>  		}
> -	} while (wait_to_complete);
> +	} while (wait_to_complete || retry-- > 0);
>  	ret = !!memcmp(&dev->data->dev_link, &dev_link,
>  		       sizeof(struct rte_eth_link));
>  	dev->data->dev_link = dev_link;
> --
> 1.8.3.1


  reply	other threads:[~2019-10-16  7:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04  9:16 [dpdk-dev] [PATCH] " Moti Haimovsky
2019-10-16  7:34 ` [dpdk-dev] [PATCH v2] " Moti Haimovsky
2019-10-16  7:42   ` Slava Ovsiienko [this message]
2019-10-20 10:07   ` Raslan Darawsheh

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=AM4PR05MB326562B2F5645775D19CBAEFD2920@AM4PR05MB3265.eurprd05.prod.outlook.com \
    --to=viacheslavo@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=motih@mellanox.com \
    --cc=rasland@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).