From: David Marchand <david.marchand@redhat.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
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>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [PATCH] common/mlx5: decrease log level for hlist creation
Date: Wed, 17 Nov 2021 14:02:28 +0100 [thread overview]
Message-ID: <CAJFAV8x-WQh_fETLMuuimNmBuJAeZhUEn=YoSpr153ye6nRfcQ@mail.gmail.com> (raw)
In-Reply-To: <DM6PR12MB375324E96EE887793265C84BDF9A9@DM6PR12MB3753.namprd12.prod.outlook.com>
On Wed, Nov 17, 2021 at 1:14 PM Slava Ovsiienko <viacheslavo@nvidia.com> wrote:
>
> 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?
That's something Maxime can see on RHEL8 with CX6 devices.
I remember seeing it too in the (recent) past, probably when working
with our QE.
So far, I did not associate this log presence to functional issues.
Looking at DPDK mailing lists:
http://inbox.dpdk.org/dev/?q=%220xFFFF+is+not+power+of+2%22
http://inbox.dpdk.org/users/?q=%220xFFFF+is+not+power+of+2%22
So we are not the only ones seeing 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| ?
I don't mind.
Logs were coming from OVS unit tests but the same can most likely be
reproduced with testpmd.
--
David Marchand
next prev parent reply other threads:[~2021-11-17 13:10 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
2021-11-17 13:02 ` David Marchand [this message]
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='CAJFAV8x-WQh_fETLMuuimNmBuJAeZhUEn=YoSpr153ye6nRfcQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@nvidia.com \
--cc=maxime.coquelin@redhat.com \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.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).