From: Stephen Hemminger <stephen@networkplumber.org>
To: fengchengwen <fengchengwen@huawei.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>,
Bruce Richardson <bruce.richardson@intel.com>,
Neil Horman <nhorman@tuxdriver.com>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH v2] eal: add destructor to unregister tailq on unload
Date: Wed, 10 Jun 2026 08:57:49 -0700 [thread overview]
Message-ID: <20260610085749.7bb0a4f3@phoenix.local> (raw)
In-Reply-To: <bfa31475-848f-42af-bfb4-f796433c3073@huawei.com>
On Wed, 10 Jun 2026 09:19:42 +0800
fengchengwen <fengchengwen@huawei.com> wrote:
> >
> > +RTE_EXPORT_SYMBOL(rte_eal_tailq_unregister)
>
> this should be with EXPERIMENTAL
Not possible, this is part of the EAL_REGISTER_TAILQ macro and usage
is under the covers. So if anything was marked experimental it would
fail code that did not allow experimental
>
> > +void
> > +rte_eal_tailq_unregister(struct rte_tailq_elem *t)
> > +{
> > + TAILQ_REMOVE(&rte_tailq_elem_head, t, next);
>
> We need first make sure it exist the tailq, just like TAILQ_FOREACH rte_eal_tailq_local_register()
Ok cheap scan since not in critical path.
next prev parent reply other threads:[~2026-06-10 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 15:04 [PATCH] eal: add destructor to unregister tailq on unload Stephen Hemminger
2026-06-08 7:57 ` Bruce Richardson
2026-06-09 9:18 ` David Marchand
2026-06-09 14:26 ` [PATCH v2] " Stephen Hemminger
2026-06-10 1:19 ` fengchengwen
2026-06-10 15:57 ` Stephen Hemminger [this message]
2026-06-09 15:53 ` [PATCH v3 0/2] eal: tailq fixes Stephen Hemminger
2026-06-09 15:53 ` [PATCH v3 1/2] eal: fix off by one in in tailq name init Stephen Hemminger
2026-06-10 1:35 ` fengchengwen
2026-06-09 15:53 ` [PATCH v3 2/2] eal: add destructor to unregister tailq on unload Stephen Hemminger
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=20260610085749.7bb0a4f3@phoenix.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=nhorman@tuxdriver.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.