From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
To: <dev@dpdk.org>
Cc: <wathsala.vithanage@arm.com>, <mb@smartsharesystems.com>
Subject: [PATCH v5 0/2] few improvemnts for SORING lib
Date: Tue, 5 May 2026 16:47:13 +0100 [thread overview]
Message-ID: <20260505154728.82235-1-konstantin.ananyev@huawei.com> (raw)
In-Reply-To: <20260423091625.123642-1-konstantin.ananyev@huawei.com>
v4 -> v5
- Fix formal API comments (Morten, Stephen/AI)
- Add 2 new test-cases for peek API (Stephen/AI)
v3 -> v4
- Remove too aggressive optimization (patch #1)
- Fix AI review comments
v2 -> v3
- fix MSVC complaints
v1 -> v2
- fix formal API comments (doxygen complaints)
- add section to release notes
First patch aims to improve enqueue/dequeue performance, specially
for the cases with multiple workers lcores per stage.
Second one introduces 'Peek API' similar to what we have for
conventional rte_ring. Also it adds new test-cases for this new API.
Konstantin Ananyev (2):
ring: make soring to always finalize its own stage
ring: introduce peek API for soring
app/test/meson.build | 1 +
app/test/test_soring.c | 107 ++++++++++
app/test/test_soring_mt_stress.c | 74 +++++++
app/test/test_soring_peek_stress.c | 75 +++++++
app/test/test_soring_stress.c | 3 +
app/test/test_soring_stress.h | 1 +
app/test/test_soring_stress_impl.h | 87 +-------
doc/guides/rel_notes/release_26_07.rst | 8 +
lib/ring/rte_soring.h | 269 ++++++++++++++++++++++++
lib/ring/soring.c | 272 ++++++++++++++++++++++---
10 files changed, 789 insertions(+), 108 deletions(-)
create mode 100644 app/test/test_soring_peek_stress.c
--
2.51.0
next prev parent reply other threads:[~2026-05-05 15:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 17:16 [PATCH v1 0/2] few improvemnts for SORING lib Konstantin Ananyev
2026-04-15 17:16 ` [PATCH v1 1/2] ring: make soring to finalize its own stage only Konstantin Ananyev
2026-04-15 17:16 ` [PATCH v1 2/2] ring: introduce peek API for soring Konstantin Ananyev
2026-04-16 19:14 ` [PATCH v2 0/2] few improvemnts for SORING lib Konstantin Ananyev
2026-04-16 19:14 ` [PATCH v2 1/2] ring: make soring to finalize its own stage only Konstantin Ananyev
2026-04-16 19:14 ` [PATCH v2 2/2] ring: introduce peek API for soring Konstantin Ananyev
2026-04-17 21:23 ` [PATCH v3 0/2] few improvemnts for SORING lib Konstantin Ananyev
2026-04-17 21:23 ` [PATCH v3 1/2] ring: make soring to finalize its own stage only Konstantin Ananyev
2026-04-17 21:23 ` [PATCH v3 2/2] ring: introduce peek API for soring Konstantin Ananyev
2026-04-18 3:28 ` [PATCH v3 0/2] few improvemnts for SORING lib Stephen Hemminger
2026-04-23 9:16 ` [PATCH v4 " Konstantin Ananyev
2026-04-23 9:16 ` [PATCH v4 1/2] ring: make soring to always finalize its own stage Konstantin Ananyev
2026-04-28 11:54 ` Morten Brørup
2026-04-23 9:16 ` [PATCH v4 2/2] ring: introduce peek API for soring Konstantin Ananyev
2026-04-28 12:56 ` Morten Brørup
2026-05-05 15:45 ` Konstantin Ananyev
2026-04-29 15:57 ` [PATCH v4 0/2] few improvemnts for SORING lib Stephen Hemminger
2026-05-05 15:47 ` Konstantin Ananyev [this message]
2026-05-05 15:47 ` [PATCH v5 1/2] ring: make soring to always finalize its own stage Konstantin Ananyev
2026-05-05 15:47 ` [PATCH v5 2/2] ring: introduce peek API for soring Konstantin Ananyev
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=20260505154728.82235-1-konstantin.ananyev@huawei.com \
--to=konstantin.ananyev@huawei.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=wathsala.vithanage@arm.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