DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
To: Robin Jarry <rjarry@redhat.com>, <dev@dpdk.org>
Subject: Re: [PATCH dpdk v3] fib6: implement RCU rule reclamation
Date: Wed, 29 Oct 2025 10:05:04 +0000	[thread overview]
Message-ID: <909f51dc-aa74-4cdf-8799-13c7e777117f@intel.com> (raw)
In-Reply-To: <20251028173703.548656-3-rjarry@redhat.com>

Acked-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>

On 10/28/2025 5:37 PM, Robin Jarry wrote:
> Currently, for the TRIE algorithm, the tbl8 group is freed even though
> the readers might be using the tbl8 group entries. The freed tbl8 group
> can be reallocated quickly. As a result, lookup may be performed
> incorrectly.
>
> Integrate RCU QSBR support in rte_fib6 objects to support safe tbl8
> group reclamation.
>
> Signed-off-by: Robin Jarry <rjarry@redhat.com>
> ---
>
> Notes:
>      v3:
>      
>      - Added release notes.
>      - Added missing break.
>      - Updated RTE_EXPORT_EXPERIMENTAL_SYMBOL version tag to 25.11.
>      
>      v2:
>      
>      - Fixed typos in docstrings.
>      - Tests depend on: http://patches.dpdk.org/project/dpdk/list/?series=36356
>
>   app/test/test_fib6.c                   | 214 +++++++++++++++++++++++++
>   doc/guides/rel_notes/release_25_11.rst |   4 +
>   lib/fib/rte_fib6.c                     |  15 ++
>   lib/fib/rte_fib6.h                     |  52 ++++++
>   lib/fib/trie.c                         |  90 ++++++++++-
>   lib/fib/trie.h                         |   8 +
>   6 files changed, 376 insertions(+), 7 deletions(-)
>
-- 
Regards,
Vladimir


      reply	other threads:[~2025-10-29 10:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 14:53 [RFC PATCH dpdk] " Robin Jarry
2025-10-10  8:55 ` Robin Jarry
2025-10-14 18:07   ` Medvedkin, Vladimir
2025-10-14 18:16 ` Medvedkin, Vladimir
2025-10-28 17:37 ` [PATCH dpdk v3] " Robin Jarry
2025-10-29 10:05   ` Medvedkin, Vladimir [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=909f51dc-aa74-4cdf-8799-13c7e777117f@intel.com \
    --to=vladimir.medvedkin@intel.com \
    --cc=dev@dpdk.org \
    --cc=rjarry@redhat.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).