From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ori Kam <orika@nvidia.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v6] ethdev: replace bit shifts with macros
Date: Wed, 20 Oct 2021 18:48:47 +0100 [thread overview]
Message-ID: <6bbe6524-e3e5-b662-6a58-bc0c6728077d@intel.com> (raw)
In-Reply-To: <20211020145517.1405713-1-ferruh.yigit@intel.com>
On 10/20/2021 3:55 PM, Ferruh Yigit wrote:
> From: Thomas Monjalon <thomas@monjalon.net>
>
> The macros RTE_BIT32 and RTE_BIT64 are used to replace bit shifts.
> The macro UINT64C is also used to replace remaining occurrences of ULL.
>
> The bit shifts of ETH_RSS_LEVEL_* are kept for aesthetic reason.
>
> The API of rte_mtr and rte_tm is using enums for 64-bit variables.
> As they are enums, unsigned bit cannot be used.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-10-20 17:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 21:04 [dpdk-dev] [PATCH] " Thomas Monjalon
2021-09-16 6:52 ` Andrew Rybchenko
2021-09-16 8:55 ` Thomas Monjalon
2021-09-16 9:36 ` Andrew Rybchenko
2021-09-23 9:39 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2021-10-05 19:18 ` Thomas Monjalon
2021-10-07 10:07 ` Andrew Rybchenko
2021-10-07 11:07 ` Ferruh Yigit
2021-10-07 13:26 ` [dpdk-dev] [PATCH v3] " Thomas Monjalon
2021-10-07 14:11 ` Thomas Monjalon
2021-10-07 15:48 ` [dpdk-dev] [PATCH v4] " Thomas Monjalon
2021-10-07 17:32 ` Ferruh Yigit
2021-10-07 18:29 ` Thomas Monjalon
2021-10-13 7:52 ` [dpdk-dev] [PATCH v5] " Thomas Monjalon
2021-10-13 11:29 ` Ferruh Yigit
2021-10-20 14:55 ` [dpdk-dev] [PATCH v6] " Ferruh Yigit
2021-10-20 17:48 ` Ferruh Yigit [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=6bbe6524-e3e5-b662-6a58-bc0c6728077d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
/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).