From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>, <viacheslavo@nvidia.com>,
<bingz@nvidia.com>, <suanmingm@nvidia.com>
Subject: Re: [PATCH] net/mlx5: optimize counters ID greneration logic
Date: Tue, 3 Jun 2025 16:51:59 +0200 [thread overview]
Message-ID: <20250603145159.fepgjp4z6dj5slkw@ds-vm-debian.local> (raw)
In-Reply-To: <20250425155515.2635090-1-akozyrev@nvidia.com>
Hi,
On Fri, Apr 25, 2025 at 06:55:12PM +0300, Alexander Kozyrev wrote:
> Enqueue generated counter IDs on a ring in bulk.
> Generate them and store in an array before putting them
> on a ring all at once. That bring better cache access
> and speeds up the mlx5_hws_cnt_pool_create() function.
>
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Best regards,
Dariusz Sosnowski
next prev parent reply other threads:[~2025-06-03 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 15:55 Alexander Kozyrev
2025-06-03 14:51 ` Dariusz Sosnowski [this message]
2025-06-04 14:59 ` Raslan Darawsheh
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=20250603145159.fepgjp4z6dj5slkw@ds-vm-debian.local \
--to=dsosnowski@nvidia.com \
--cc=akozyrev@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=rasland@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).