From: Erez Ferber <erezferber@gmail.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>
Cc: "Daniel Östman" <daniel.ostman@ericsson.com>,
"users@dpdk.org" <users@dpdk.org>,
"Matan Azrad" <matan@nvidia.com>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: Re: mlx5: imissed / out_of_buffer counter always 0
Date: Mon, 5 Jun 2023 13:29:21 +0300 [thread overview]
Message-ID: <CAF5_M5jD0Er_i_Zq8hRagR5QjU88iEGFQEOBuYtOSXZa+TQFBQ@mail.gmail.com> (raw)
In-Reply-To: <DM6PR12MB37534448D839810FBD8E254DDF4EA@DM6PR12MB3753.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2587 bytes --]
Hi Daniel,
is the container running in shared or non-shared mode ?
For shared mode, I assume the kernel sysfs counters which DPDK relies on
for imissed/out_of_buffer are not exposed.
Best regards,
Erez
On Fri, 2 Jun 2023 at 18:07, Slava Ovsiienko <viacheslavo@nvidia.com> wrote:
> Hi, Daniel
>
>
>
> I would recommend to take the following action:
>
> - update the firmware, 16.33.xxxx looks to be outdated a little bit.
> Please, try 16.35.1012 or later.
> mlx5_glue->devx_obj_create might succeed with the newer FW.
>
> - try to specify dv_flow_en=0 devarg, it forces mlx5 PMD to use rdma_core
> library for queue management
> and kernel driver will be aware about Rx queues being created and attach
> them to the kernel counter set
>
>
>
> With best regards,
> Slava
>
>
>
> *From:* Daniel Östman <daniel.ostman@ericsson.com>
> *Sent:* Friday, June 2, 2023 3:59 PM
> *To:* users@dpdk.org
> *Cc:* Matan Azrad <matan@nvidia.com>; Slava Ovsiienko <
> viacheslavo@nvidia.com>; maxime.coquelin@redhat.com;
> david.marchand@redhat.com
> *Subject:* mlx5: imissed / out_of_buffer counter always 0
>
>
>
> Hi,
>
>
>
> I’m deploying a containerized DPDK application in an OpenShift Kubernetes
> environment using DPDK 21.11.3.
>
> The application uses a Mellanox ConnectX-5 100G NIC through VFs.
>
>
>
> The problem I have is that the ETH stats counter imissed (which seems to
> be mapped to “out_of_buffer” internally in mlx5 PMD driver) is 0 when I
> don’t expect it to be, i.e. when the application doesn’t read the packets
> fast enough.
>
>
>
> Using GDB I can see that it tries to access the counter through
> /sys/class/infiniband/mlx5_99/ports/1/hw_counters/out_of_buffer but the
> hw_counters directory is missing so it will just return a zero value. I
> don’t know why it is missing.
>
> When looking at mlx5_os_read_dev_stat() I can see that there is an
> alternative way of reading the counter, through
> mlx5_devx_cmd_queue_counter_query() but under the condition that
> priv->q_counters are set.
>
> It doesn’t get set in my case because mlx5_glue->devx_obj_create() fails
> (errno 22) in mlx5_devx_cmd_queue_counter_alloc().
>
>
>
> Have I missed something?
>
>
>
> NIC info:
>
> Mellanox Technologies MT27800 Family [ConnectX-5] - 100Gb 2-port QSFP28
> MCX516A-CCHT
> driver: mlx5_core
> version: 5.0-0
> firmware-version: 16.33.1048 (MT_0000000417)
>
>
>
> Please let me know if I need to provide more information.
>
>
>
> Best regards,
>
> Daniel
>
>
>
[-- Attachment #2: Type: text/html, Size: 5188 bytes --]
next prev parent reply other threads:[~2023-06-05 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 12:59 Daniel Östman
2023-06-02 15:07 ` Slava Ovsiienko
2023-06-05 10:29 ` Erez Ferber [this message]
2023-06-05 14:00 ` Daniel Östman
2023-06-21 20:22 ` Maxime Coquelin
2023-06-22 15:47 ` Maxime Coquelin
2023-08-18 12:04 ` Daniel Östman
2023-10-04 13:49 ` Maxime Coquelin
2023-11-08 12:55 ` Daniel Östman
2023-11-09 14:51 ` Slava Ovsiienko
2023-12-06 12:40 ` Daniel Östman
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=CAF5_M5jD0Er_i_Zq8hRagR5QjU88iEGFQEOBuYtOSXZa+TQFBQ@mail.gmail.com \
--to=erezferber@gmail.com \
--cc=daniel.ostman@ericsson.com \
--cc=david.marchand@redhat.com \
--cc=matan@nvidia.com \
--cc=maxime.coquelin@redhat.com \
--cc=users@dpdk.org \
--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).