DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	matan@mellanox.com, shahafs@mellanox.com
Cc: dev@dpdk.org, Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx4: use dynamic log type
Date: Fri, 24 May 2019 15:08:12 +0100	[thread overview]
Message-ID: <b8bc4980-92d8-813c-ede5-9a196d39706b@intel.com> (raw)
In-Reply-To: <20190521212712.29357-1-stephen@networkplumber.org>

On 5/21/2019 10:27 PM, Stephen Hemminger wrote:
> This driver should use dynamic log level not RTE_LOGTYPE_PMD.
> Other drivers were converted back in 18.02.
> 
> This is really a bug, all other drivers use dynamic log levels
> by now.

+1, we should switch it to dynamic log much earlier

Matan, Shahaf,

This patch will have problem with "RTE_LOG" usage, need to use rte_log() I
guess, can you (or Stephen, whoever can work on it) please send a new version?

Thanks,
ferruh

> 
> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
> ---
>  drivers/net/mlx4/mlx4.c       | 8 ++++++++
>  drivers/net/mlx4/mlx4_utils.h | 6 ++++--
>  2 files changed, 12 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/mlx4/mlx4.c b/drivers/net/mlx4/mlx4.c
> index fe559c040706..e532dc53738f 100644
> --- a/drivers/net/mlx4/mlx4.c
> +++ b/drivers/net/mlx4/mlx4.c
> @@ -60,6 +60,9 @@ static rte_spinlock_t mlx4_shared_data_lock = RTE_SPINLOCK_INITIALIZER;
>  /* Process local data for secondary processes. */
>  static struct mlx4_local_data mlx4_local_data;
>  
> +/** Driver-specific log messages type. */
> +int mlx4_logtype;
> +
>  /** Configuration structure for device arguments. */
>  struct mlx4_conf {
>  	struct {
> @@ -1272,6 +1275,11 @@ mlx4_glue_init(void)
>   */
>  RTE_INIT(rte_mlx4_pmd_init)
>  {
> +	/* Initialize driver log type. */
> +	mlx4_logtype = rte_log_register("pmd.net.mlx4");
> +	if (mlx4_logtype >= 0)
> +		rte_log_set_level(mlx4_logtype, RTE_LOG_NOTICE);
> +
>  	/*
>  	 * MLX4_DEVICE_FATAL_CLEANUP tells ibv_destroy functions we
>  	 * want to get success errno value in case of calling them
> diff --git a/drivers/net/mlx4/mlx4_utils.h b/drivers/net/mlx4/mlx4_utils.h
> index 86abb3b7e376..9d3d2a4e32a1 100644
> --- a/drivers/net/mlx4/mlx4_utils.h
> +++ b/drivers/net/mlx4/mlx4_utils.h
> @@ -15,6 +15,8 @@
>  
>  #include "mlx4.h"
>  
> +extern int mlx4_logtype;
> +
>  #ifndef NDEBUG
>  
>  /*
> @@ -35,7 +37,7 @@ pmd_drv_log_basename(const char *s)
>  }
>  
>  #define PMD_DRV_LOG(level, ...) \
> -	RTE_LOG(level, PMD, \
> +	RTE_LOG(level, mlx4_logtype, \
>  		RTE_FMT("%s:%u: %s(): " RTE_FMT_HEAD(__VA_ARGS__,) "\n", \
>  			pmd_drv_log_basename(__FILE__), \
>  			__LINE__, \
> @@ -52,7 +54,7 @@ pmd_drv_log_basename(const char *s)
>   */
>  
>  #define PMD_DRV_LOG(level, ...) \
> -	RTE_LOG(level, PMD, \
> +	RTE_LOG(level, mlx4_logtype, \
>  		RTE_FMT(MLX4_DRIVER_NAME ": " \
>  			RTE_FMT_HEAD(__VA_ARGS__,) "\n", \
>  		RTE_FMT_TAIL(__VA_ARGS__,)))
> 


  reply	other threads:[~2019-05-24 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 21:27 Stephen Hemminger
2019-05-24 14:08 ` Ferruh Yigit [this message]
2019-05-24 16:03 ` [dpdk-dev] [PATCH v2] " Stephen Hemminger
2019-05-24 17:13   ` Ferruh Yigit
2019-05-26 19:24     ` Shahaf Shuler

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=b8bc4980-92d8-813c-ede5-9a196d39706b@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=stephen@networkplumber.org \
    --cc=sthemmin@microsoft.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).