From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, "Varghese, Vipin" <Vipin.Varghese@amd.com>,
"P, Thiyagarajan" <Thiyagarajan.P@amd.com>
Subject: Re: [PATCH v3 0/2] latencystats: fix receive sample MP issues
Date: Thu, 3 Jul 2025 11:07:39 +0200 [thread overview]
Message-ID: <CAJFAV8wRCa3JodNNCRRjkEG=R+CPLovdo7AZCPXnf9gANZ7jBg@mail.gmail.com> (raw)
In-Reply-To: <20250617150252.814215-1-stephen@networkplumber.org>
On Tue, Jun 17, 2025 at 5:03 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> After investigating latencystat test failures, discovered it poorly
> designed to handle bursts and multiple queues.
>
> v3 - reduce patch changes, break a line that was too long
>
> Stephen Hemminger (2):
> latencystats: fix receive sample MP issues
> latencystats: optimize locking on transmit
>
> lib/latencystats/rte_latencystats.c | 64 +++++++++++++++++++----------
> 1 file changed, 43 insertions(+), 21 deletions(-)
Series applied, thanks.
--
David Marchand
prev parent reply other threads:[~2025-07-03 9:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 0:34 [PATCH 0/2] Latencystat optimization and fix Stephen Hemminger
2025-06-13 0:34 ` [PATCH 1/2] latencystats: fix receive sample MP issues Stephen Hemminger
2025-06-13 0:34 ` [PATCH 2/2] latencystats: optimize locking on transmit Stephen Hemminger
2025-06-13 11:13 ` [PATCH 0/2] Latencystat optimization and fix Varghese, Vipin
2025-06-16 16:04 ` [PATCH v2 0/2] Latencystats optimizations " Stephen Hemminger
2025-06-16 16:04 ` [PATCH v2 1/2] latencystats: fix receive sample MP issues Stephen Hemminger
2025-06-16 16:04 ` [PATCH v2 2/2] latencystats: optimize locking on transmit Stephen Hemminger
2025-06-17 15:00 ` [PATCH v3 0/2] latencystats: fix receive sample MP issues Stephen Hemminger
2025-06-17 15:00 ` [PATCH v3 1/2] " Stephen Hemminger
2025-06-25 11:31 ` Varghese, Vipin
2025-06-26 15:01 ` Stephen Hemminger
2025-06-27 2:05 ` Varghese, Vipin
2025-06-17 15:00 ` [PATCH v3 2/2] latencystats: optimize locking on transmit Stephen Hemminger
2025-07-03 9:07 ` David Marchand [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='CAJFAV8wRCa3JodNNCRRjkEG=R+CPLovdo7AZCPXnf9gANZ7jBg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=Thiyagarajan.P@amd.com \
--cc=Vipin.Varghese@amd.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).