From: Stephen Hemminger <stephen@networkplumber.org>
To: Felipe Pereira <felipe@spint.com.br>
Cc: users@dpdk.org
Subject: Re: Items stuck at rte_hash
Date: Thu, 1 May 2025 08:15:24 -0700 [thread overview]
Message-ID: <20250501081524.53c30800@hermes.local> (raw)
In-Reply-To: <824beca1-a48b-42e5-ac20-05ad17fc3435@spint.com.br>
On Thu, 1 May 2025 11:16:25 -0300
Felipe Pereira <felipe@spint.com.br> wrote:
> static int cleanup_timeout()
> {
> const uint64_t now = rte_get_timer_cycles();
> const uint64_t cutoff = now - CLEANUP_TIMEOUT_CYCLES;
>
> uint32_t iter = 0;
> const void *key;
> void *data;
> uint64_t expired_keys[MAX_EXPIRED_KEYS];
> int expired_count = 0;
> rte_atomic32_set(¬_found_keys, 0);
I don't think your main thread registered it self with RCU.
It probably needs to
prev parent reply other threads:[~2025-05-01 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 14:16 Felipe Pereira
2025-05-01 15:15 ` 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=20250501081524.53c30800@hermes.local \
--to=stephen@networkplumber.org \
--cc=felipe@spint.com.br \
--cc=users@dpdk.org \
/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).