From: Wisam Monther <wisamm@nvidia.com>
To: Harold Huang <baymaxhuang@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] app/flow-perf: replace RTE_BE32/16 with rte_cpu_to_be_32/16 for variables
Date: Mon, 27 Mar 2023 10:29:38 +0000 [thread overview]
Message-ID: <CH0PR12MB50251FEA4BE7D5DAC9D94892A48B9@CH0PR12MB5025.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230312020009.288-1-baymaxhuang@gmail.com>
Hi,
> -----Original Message-----
> From: Harold Huang <baymaxhuang@gmail.com>
> Sent: Sunday, March 12, 2023 4:00 AM
> To: dev@dpdk.org
> Cc: Harold Huang <baymaxhuang@gmail.com>; Wisam Monther
> <wisamm@nvidia.com>
> Subject: [PATCH] app/flow-perf: replace RTE_BE32/16 with
> rte_cpu_to_be_32/16 for variables
>
> In DPDK, the macros RTE_BE32 or RTE_BE16 are usually used for constant
> values. And functions such as rte_cpu_to_be_32 or
> rte_cpu_to_be_16 are optimized for variables.
>
> Signed-off-by: Harold Huang <baymaxhuang@gmail.com>
> ---
> app/test-flow-perf/actions_gen.c | 28 ++++++++++++++--------------
> app/test-flow-perf/items_gen.c | 2 +-
> 2 files changed, 15 insertions(+), 15 deletions(-)
>
Indeed your change is in the correct files and I agree that it's need to be done,
But you are not doing it for all RTE_BE32 and RTE_BE16 in the app or the same files
After quick search I see:
app/test-flow-perf/items_gen.c:12
app/test-flow-perf/actions_gen.c:29
While you are doing the change only for:
app/test-flow-perf/items_gen.c:1
app/test-flow-perf/actions_gen.c:14
Can you please extend your fix for all needed vars.
BRs,
Wisam Jaddo
next prev parent reply other threads:[~2023-03-27 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 2:00 Harold Huang
2023-03-27 10:29 ` Wisam Monther [this message]
2023-03-27 12:32 ` Harold Huang
2023-04-18 11:32 ` Wisam Monther
2024-10-07 19:36 ` 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=CH0PR12MB50251FEA4BE7D5DAC9D94892A48B9@CH0PR12MB5025.namprd12.prod.outlook.com \
--to=wisamm@nvidia.com \
--cc=baymaxhuang@gmail.com \
--cc=dev@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).