From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Kiran Kumar K <kirankumark@marvell.com>
Cc: dev@dpdk.org, Ori Kam <orika@nvidia.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [PATCH] ethdev: fix Tx queue mask endianness
Date: Thu, 29 Jun 2023 17:31:09 +0200 [thread overview]
Message-ID: <4981207.a9HWlOh95j@thomas> (raw)
In-Reply-To: <20230629135839.974700-1-david.marchand@redhat.com>
29/06/2023 15:58, David Marchand:
> Even if harmless, this endianness tag is incorrect as the tx_queue field
> is declared as a host integer.
> Additionally, this breaks OVS compilation with sparse.
>
> Fixes: 41f6bdc7615a ("ethdev: add Tx queue flow matching item")
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> lib/ethdev/rte_flow.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h
> index 3fe57140f9..86ed98c562 100644
> --- a/lib/ethdev/rte_flow.h
> +++ b/lib/ethdev/rte_flow.h
> @@ -2307,7 +2307,7 @@ struct rte_flow_item_tx_queue {
> /** Default mask for RTE_FLOW_ITEM_TX_QUEUE. */
> #ifndef __cplusplus
> static const struct rte_flow_item_tx_queue rte_flow_item_tx_queue_mask = {
> - .tx_queue = RTE_BE16(0xffff),
> + .tx_queue = 0xffff,
As I said in an earlier comment about the same issue,
UINT16_MAX would be better.
next prev parent reply other threads:[~2023-06-29 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 13:58 [PATCH] ethdev: fix Tx queue mask endianness David Marchand
2023-06-29 14:48 ` Ferruh Yigit
2023-06-29 15:31 ` Thomas Monjalon [this message]
2023-06-29 15:40 ` David Marchand
2023-06-29 15:42 ` Thomas Monjalon
2023-06-29 16:14 ` Ferruh Yigit
2023-06-30 7:00 ` David Marchand
2023-06-30 7:13 ` David Marchand
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=4981207.a9HWlOh95j@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=kirankumark@marvell.com \
--cc=orika@nvidia.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 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.