From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: David Marchand <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
Matan Azrad <matan@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>
Subject: RE: [PATCH] common/mlx5: decrease log level for hlist creation
Date: Wed, 17 Nov 2021 12:14:47 +0000 [thread overview]
Message-ID: <DM6PR12MB375324E96EE887793265C84BDF9A9@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211116203354.14167-1-david.marchand@redhat.com>
Hi, David
In general, I'm OK with lowering the log level.
But we do not expect the warning " is not power of 2".
What mlx5_hlist_create() call caused this?
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Tuesday, November 16, 2021 22:34
> To: dev@dpdk.org
> Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>;
> ferruh.yigit@intel.com; Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Suanming Mou <suanmingm@nvidia.com>
> Subject: [PATCH] common/mlx5: decrease log level for hlist creation
>
> Initialising mlx5 devices in OVS, I get the following logs:
> 2021-11-16T20:08:37Z|00021|dpdk|INFO|EAL: Probe PCI driver: mlx5_pci
> (15b3:101d) device: 0000:3b:00.0 (socket 0)
> 2021-11-16T20:08:37Z|00022|dpdk|INFO|common_mlx5: RTE_MEM is
> selected.
> 2021-11-16T20:08:38Z|00023|dpdk|WARN|mlx5_pci: Size 0xFFFF is not
> power of 2, will be aligned to 0x10000.
Can we remove not too meaningful details from commit message?
Date/time in messages: 2021-11-16T20:08:38Z|00023| ?
With best regards,
Slava
>
> Those logs just make no sense for a final user and were raised to WARN level
> recently.
> Lower them back to DEBUG.
>
> Fixes: 961b6774c451 ("common/mlx5: add per-lcore cache to hash list
> utility")
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> drivers/common/mlx5/mlx5_common_utils.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/common/mlx5/mlx5_common_utils.c
> b/drivers/common/mlx5/mlx5_common_utils.c
> index 775fabd478..c83333b4b4 100644
> --- a/drivers/common/mlx5/mlx5_common_utils.c
> +++ b/drivers/common/mlx5/mlx5_common_utils.c
> @@ -406,7 +406,7 @@ mlx5_hlist_create(const char *name, uint32_t size,
> bool direct_key,
> /* Align to the next power of 2, 32bits integer is enough now. */
> if (!rte_is_power_of_2(size)) {
> act_size = rte_align32pow2(size);
> - DRV_LOG(WARNING, "Size 0x%" PRIX32 " is not power of 2,
> will "
> + DRV_LOG(DEBUG, "Size 0x%" PRIX32 " is not power of 2, will
> "
> "be aligned to 0x%" PRIX32 ".", size, act_size);
> } else {
> act_size = size;
> --
> 2.23.0
next prev parent reply other threads:[~2021-11-17 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 20:33 David Marchand
2021-11-16 21:33 ` Stephen Hemminger
2021-11-17 12:14 ` Slava Ovsiienko [this message]
2021-11-17 13:02 ` David Marchand
2021-11-17 13:28 ` Slava Ovsiienko
2021-11-17 14:46 ` David Marchand
2021-11-18 14:22 ` David Marchand
2021-11-19 8:36 ` Slava Ovsiienko
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=DM6PR12MB375324E96EE887793265C84BDF9A9@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
/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).