From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Shani Peretz <shperetz@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Maayan Kashani <mkashani@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Anatoly Burakov <anatoly.burakov@intel.com>
Subject: RE: [PATCH] net/mlx5: add hairpin counter per queue
Date: Wed, 11 Sep 2024 07:25:08 +0000 [thread overview]
Message-ID: <CH3PR12MB84605EAC76C75C7C72529FE2A49B2@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240910074051.5691-1-shperetz@nvidia.com>
> -----Original Message-----
> From: Shani Peretz <shperetz@nvidia.com>
> Sent: Tuesday, September 10, 2024 09:41
> To: dev@dpdk.org
> Cc: Shani Peretz <shperetz@nvidia.com>; Maayan Kashani
> <mkashani@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>; Dariusz
> Sosnowski <dsosnowski@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Bing Zhao <bingz@nvidia.com>; Ori Kam
> <orika@nvidia.com>; Suanming Mou <suanmingm@nvidia.com>; Matan
> Azrad <matan@nvidia.com>; Anatoly Burakov <anatoly.burakov@intel.com>
> Subject: [PATCH] net/mlx5: add hairpin counter per queue
>
> Currently mlx5 PMD exposes hairpin_out_of_buffer counter that specifically
> tracks packets dropped when hairpin Rx queue is full.
>
> This patch allows the user to choose whether they want to track packet drops
> at a per-port level or a per-queue level.
>
> If the user chooses to have a counter per queue, HW objects will be created for
> each individual queue, and each Rx queue will be assigned to its specific
> counter.
>
> However, if the user has more hairpin Rx queues than available hardware
> counters, we will attach the first hairpin queues to the available counters, and
> the remaining queues will not have their packet drops tracked by these
> counters.
>
> This approach provides flexibility for users to monitor packet drops at either a
> port-level or a queue-level granularity.
>
> Signed-off-by: Shani Peretz <shperetz@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Best regards,
Dariusz Sosnowski
prev parent reply other threads:[~2024-09-11 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 7:40 Shani Peretz
2024-09-11 7:25 ` Dariusz Sosnowski [this message]
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=CH3PR12MB84605EAC76C75C7C72529FE2A49B2@CH3PR12MB8460.namprd12.prod.outlook.com \
--to=dsosnowski@nvidia.com \
--cc=anatoly.burakov@intel.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=shperetz@nvidia.com \
--cc=suanmingm@nvidia.com \
--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).