From: Stephen Hemminger <stephen@networkplumber.org>
To: Robin Jarry <rjarry@redhat.com>
Cc: dev@dpdk.org, Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Subject: Re: [PATCH dpdk] fib: expose tbl8 usage statistics
Date: Tue, 8 Sep 2026 10:31:00 -0700 [thread overview]
Message-ID: <20260908103100.3bf817f5@phoenix.local> (raw)
In-Reply-To: <20260224133340.1638295-2-rjarry@redhat.com>
On Tue, 24 Feb 2026 14:33:41 +0100
Robin Jarry <rjarry@redhat.com> wrote:
> Both dir24_8 (IPv4) and trie (IPv6) algorithms already track tbl8 group
> allocation internally but there is no way for applications to query this
> information. Monitoring tbl8 usage is important to detect exhaustion
> before route insertions start failing.
>
> Add rte_fib_tbl8_get_stats() and rte_fib6_tbl8_get_stats() to let
> applications retrieve the number of tbl8 groups currently in use and the
> total capacity. For dir24_8, the used count comes from cur_tbl8s. For
> trie, it comes from tbl8_pool_pos which reflects the actual number of
> allocated entries since the pool is a stack.
>
> Add unit tests for both functions covering invalid arguments, unsupported
> FIB types and verifying that the used count changes correctly after route
> insertions and deletions.
>
> Signed-off-by: Robin Jarry <rjarry@redhat.com>
Exposing fib usage statistics is good idea but rather than returning statistics
individually as call pointers, it would be better to have new statistics
structure similar to ethdev xstats with name and value. That would allow
for expansion and be generic against table implementations.
prev parent reply other threads:[~2026-09-08 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 13:33 [PATCH dpdk] fib: expose tbl8 usage statistics Robin Jarry
2026-09-08 17:31 ` Stephen Hemminger [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=20260908103100.3bf817f5@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=rjarry@redhat.com \
--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