DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Cui, LunyuanX" <lunyuanx.cui@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Yang, Qiming" <qiming.yang@intel.com>,
	"Cui, LunyuanX" <lunyuanx.cui@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/ixgbe: fixed port can not link up in FreeBSD
Date: Thu, 12 Dec 2019 11:15:59 +0000	[thread overview]
Message-ID: <DM6PR11MB25565D48CC298A570584EECA9A550@DM6PR11MB2556.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20191212111714.533-1-lunyuanx.cui@intel.com>

Hi,

> 
> In FreeBSD environment, nic_uio drivers do not support interrupts,
> rte_intr_callback_register() will fail to register interrupts.
> We can not make link status to change from down to up by interrupt
> callback. So we need to wait for the controller to acquire link
> when ports start. Through multiple tests, 5s should be enough.
> 
> Fixes: b9bd0f09fa15 ("ethdev: fix link status query")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Lunyuan Cui <lunyuanx.cui@intel.com>
> ---
>  drivers/net/ixgbe/ixgbe_ethdev.c | 22 ++++++++++++++++++++++
>  1 file changed, 22 insertions(+)
> 
> diff --git a/drivers/net/ixgbe/ixgbe_ethdev.c b/drivers/net/ixgbe/ixgbe_ethdev.c
> index 2c6fd0f13..e33b5483c 100644
> --- a/drivers/net/ixgbe/ixgbe_ethdev.c
> +++ b/drivers/net/ixgbe/ixgbe_ethdev.c
> @@ -2555,6 +2555,9 @@ ixgbe_dev_start(struct rte_eth_dev *dev)
>  		IXGBE_DEV_PRIVATE_TO_TM_CONF(dev->data->dev_private);
>  	struct ixgbe_macsec_setting *macsec_setting =
>  		IXGBE_DEV_PRIVATE_TO_MACSEC_SETTING(dev->data->dev_private);
> +#ifdef RTE_EXEC_ENV_FREEBSD
> +	int i;
> +#endif
> 
>  	PMD_INIT_FUNC_TRACE();
> 
> @@ -2801,6 +2804,25 @@ ixgbe_dev_start(struct rte_eth_dev *dev)
>  			    "please call hierarchy_commit() "
>  			    "before starting the port");
> 
> +#ifdef RTE_EXEC_ENV_FREEBSD
> +	/*
> +	 * In freebsd environment, nic_uio drivers do not support interrupts,
> +	 * rte_intr_callback_register() will fail to register interrupts.
> +	 * We can not make link status to change from down to up by interrupt
> +	 * callback. So we need to wait for the controller to acquire link
> +	 * when ports start.
> +	 */
> +	for (i = 0; i < 25; i++) {
> +		/* If link up, just jump out */
> +		err = ixgbe_check_link(hw, &speed, &link_up, 0);
> +		if (err)
> +			goto error;
> +		if (link_up)
> +			break;
> +		msec_delay(200);
> +	}
> +#endif

Might be better to put it into a separate function to keep start() code clean.
Konstantin

> +
>  	/*
>  	 * Update link status right before return, because it may
>  	 * start link configuration process in a separate thread.
> --
> 2.17.1


  reply	other threads:[~2019-12-12 11:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12 11:17 Lunyuan Cui
2019-12-12 11:15 ` Ananyev, Konstantin [this message]
2019-12-13  2:36 ` [dpdk-dev] [PATCH v2] " Lunyuan Cui
2019-12-13 14:32   ` Ananyev, Konstantin
2019-12-16  2:24 ` [dpdk-dev] [PATCH v3] net/ixgbe: fix " Lunyuan Cui
2019-12-18  2:47   ` Ye Xiaolong
2019-12-18 10:21   ` Ananyev, Konstantin
  -- strict thread matches above, loose matches on Subject: below --
2019-12-11 15:18 [dpdk-dev] [PATCH] net/ixgbe: fixed " Lunyuan Cui

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=DM6PR11MB25565D48CC298A570584EECA9A550@DM6PR11MB2556.namprd11.prod.outlook.com \
    --to=konstantin.ananyev@intel.com \
    --cc=dev@dpdk.org \
    --cc=lunyuanx.cui@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=stable@dpdk.org \
    --cc=wenzhuo.lu@intel.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).