DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Robin Jarry <rjarry@redhat.com>
Cc: <dev@dpdk.org>, Ciara Power <ciara.power@intel.com>
Subject: Re: [PATCH dpdk] telemetry: fix adding dicts in container arrays
Date: Thu, 8 Jan 2026 09:20:21 +0000	[thread overview]
Message-ID: <aV921VEaX5uQW1yH@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260107215129.1329960-2-rjarry@redhat.com>

On Wed, Jan 07, 2026 at 10:51:30PM +0100, Robin Jarry wrote:
> Currently, adding TEL_DICT containers in TEL_ARRAY_CONTAINER containers
> is not supported by rte_tel_data_add_array_container. It wrongfully
> returns -EINVAL where it should allow it.
> 
> This is supported by the JSON formatter.
> 
> Allow the same value types than rte_tel_data_add_dict_container().
> 
> Fixes: c933bb5177ca ("telemetry: support array values in data object")
> 
> Signed-off-by: Robin Jarry <rjarry@redhat.com>
> ---
>  lib/telemetry/telemetry_data.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/lib/telemetry/telemetry_data.c b/lib/telemetry/telemetry_data.c
> index 0354a0654804..0a006559ab42 100644
> --- a/lib/telemetry/telemetry_data.c
> +++ b/lib/telemetry/telemetry_data.c
> @@ -96,10 +96,10 @@ int
>  rte_tel_data_add_array_container(struct rte_tel_data *d,
>  		struct rte_tel_data *val, int keep)
>  {
> -	if (d->type != TEL_ARRAY_CONTAINER ||
> -			(val->type != TEL_ARRAY_UINT
> +	if (d->type != TEL_ARRAY_CONTAINER || (val->type != TEL_ARRAY_UINT
>  			&& val->type != TEL_ARRAY_INT
> -			&& val->type != TEL_ARRAY_STRING))
> +			&& val->type != TEL_ARRAY_STRING
> +			&& val->type != TEL_DICT))
>  		return -EINVAL;
>  	if (d->data_len >= RTE_TEL_MAX_ARRAY_ENTRIES)
>  		return -ENOSPC;
> -- 

No objection to this, but previous implementation limited the options to
what was needed and tested by telemetry rather than trying to cover every
eventuality. If we now support dicts in arrays, please add some unit
testing around it to verify we haven't any issues with it.

Thanks,
/Bruce

  reply	other threads:[~2026-01-08  9:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 21:51 Robin Jarry
2026-01-08  9:20 ` Bruce Richardson [this message]
2026-01-08 10:50 ` [PATCH dpdk v2] " Robin Jarry
2026-01-08 11:06   ` Bruce Richardson
2026-01-08 11:07   ` Bruce Richardson

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=aV921VEaX5uQW1yH@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=rjarry@redhat.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).