DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Robin Jarry" <rjarry@redhat.com>
To: <dev@dpdk.org>, "Vladimir Medvedkin" <vladimir.medvedkin@intel.com>
Subject: Re: [RFC PATCH dpdk] fib6: implement RCU rule reclamation
Date: Fri, 10 Oct 2025 10:55:09 +0200	[thread overview]
Message-ID: <DDEILG4ZSB37.Q38N053PLJ4N@redhat.com> (raw)
In-Reply-To: <20250610145341.38271-2-rjarry@redhat.com>

Robin Jarry, Jun 10, 2025 at 16:53:
> Currently, for the TRIE algorithm (actually, it should be called
> DIR-24-8-8-8-8-8-8-8-8-8-8-8-8), 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.
>
> To address that, RCU QSBR is integrated for safe tbl8 group reclamation.
>
> Cc: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
> Signed-off-by: Robin Jarry <rjarry@redhat.com>
> ---
>
> Notes:
>     This is a semi-copy-paste of the FIB4 implementation.
>     
>     I couldn't understand the implementation of trie_modify with regard to
>     depth_diff handling.
>     
>     The unit tests fail because depth_diff is always 0 when deleting a route
>     which causes any subsequent add to fail with a -ENOSPC error.
>     
>     Vladimir, could you give some more insights on the matter?

Gentle bump. Hi Vladimir, could you have a look? Thanks!

-- 
Robin

> Not recommended for children.


      reply	other threads:[~2025-10-10  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 14:53 Robin Jarry
2025-10-10  8:55 ` Robin Jarry [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=DDEILG4ZSB37.Q38N053PLJ4N@redhat.com \
    --to=rjarry@redhat.com \
    --cc=dev@dpdk.org \
    --cc=vladimir.medvedkin@intel.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).