From: Stephen Hemminger <stephen@networkplumber.org>
To: Andrey Yudin <Andrey.Yudin@infotecs.ru>
Cc: Jerin Jacob <jerinj@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Zhirun Yan <yanzhirun_163@163.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Robin Jarry <rjarry@redhat.com>, <dev@dpdk.org>,
<stable@dpdk.org>
Subject: Re: [PATCH] graph: fix xstats of cloned nodes
Date: Wed, 22 Jul 2026 11:20:46 -0700 [thread overview]
Message-ID: <20260722112046.6cf64823@phoenix.local> (raw)
In-Reply-To: <20260708081420.1100574-1-Andrey.Yudin@infotecs.ru>
On Wed, 8 Jul 2026 11:14:19 +0300
Andrey Yudin <Andrey.Yudin@infotecs.ru> wrote:
> When cloning a node with xstats enabled, xstat_desc entries are copied
> into the rte_node_register structure, but the nb_xstats field is not.
>
> As a result, the cloned node reports zero available xstats,
> making xstats unusable.
>
> Copy the nb_xstats field when cloning the node so that cloned nodes
> preserve the xstats configuration of the original node.
>
> Fixes: 070db97e017b ("graph: support node xstats")
> Cc: stable@dpdk.org
> Signed-off-by: Andrey Yudin <Andrey.Yudin@infotecs.ru>
> ---
This patch is technically correct, and I have no issues with the code itself.
However, the submitter's mail domain (infotecs.ru) belongs to JSC
InfoTeCS, which is on the EU consolidated sanctions list. Whether a
contribution from a sanctioned entity can be accepted is a legal
question, and not one a maintainer has the authority to decide.
Holding off on merging this patch until there is direction from LF
legal and/or the DPDK governing board.
prev parent reply other threads:[~2026-07-22 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 8:14 [PATCH] graph: fix xstats of cloned nodes Andrey Yudin
2026-07-08 9:21 ` Robin Jarry
2026-07-15 6:32 ` kirankumark
2026-07-22 18:20 ` 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=20260722112046.6cf64823@phoenix.local \
--to=stephen@networkplumber.org \
--cc=Andrey.Yudin@infotecs.ru \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=rjarry@redhat.com \
--cc=stable@dpdk.org \
--cc=yanzhirun_163@163.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