From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: "Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Konstantin Ananyev" <konstantin.ananyev@huawei.com>
Cc: <dev@dpdk.org>
Subject: [PATCH] doc: remove cache flush threshold deprecation notice
Date: Thu, 22 Oct 2026 18:48:43 +0200 [thread overview]
Message-ID: <20261022164844.34845-1-dsosnowski@nvidia.com> (raw)
Remove the deprecation notice for flushthresh field
in struct rte_mempool_cache, which was removed in the offending commit.
Fixes: 7dbec9e69c36 ("mempool: remove deprecated cache flush threshold")
Cc: mb@smartsharesystems.com
Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
---
doc/guides/rel_notes/deprecation.rst | 3 ---
1 file changed, 3 deletions(-)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 29fb7d56d6..44826a0cf2 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -29,9 +29,6 @@ Deprecation Notices
Use the ``-S <service-corelist>`` parameter instead
to specify the cores to be used for background services in DPDK.
-* mempool: The ``flushthresh`` field in ``struct rte_mempool_cache`` is obsolete,
- and will be removed in DPDK 26.11.
-
* mempool: The object array in ``struct rte_mempool_cache`` is oversize by factor two,
and will be reduced to ``RTE_MEMPOOL_CACHE_MAX_SIZE`` in DPDK 26.11.
--
2.43.0
next reply other threads:[~2026-10-22 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 16:48 Dariusz Sosnowski [this message]
2026-10-22 17:32 ` [PATCH] doc: remove cache flush threshold deprecation notice Morten Brørup
2026-10-23 7:53 ` Dariusz Sosnowski
2026-10-23 7:51 ` [PATCH v2] doc: remove mempool deprecation notices Dariusz Sosnowski
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=20261022164844.34845-1-dsosnowski@nvidia.com \
--to=dsosnowski@nvidia.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=mb@smartsharesystems.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