From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"cristian.dumitrescu@intel.com" <cristian.dumitrescu@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"jasvinder.singh@intel.com" <jasvinder.singh@intel.com>
Subject: Re: [PATCH v3 3/5] common: add missing implementations
Date: Thu, 15 Nov 2018 08:40:08 +0000 [thread overview]
Message-ID: <20181115083955.GA4757@jerin> (raw)
In-Reply-To: <369642722f3c4d3d6c184fddb34b4aa7ce308a84.1542213812.git.anatoly.burakov@intel.com>
-----Original Message-----
> Date: Wed, 14 Nov 2018 16:47:08 +0000
> From: Anatoly Burakov <anatoly.burakov@intel.com>
> To: dev@dpdk.org
> CC: cristian.dumitrescu@intel.com, thomas@monjalon.net,
> bruce.richardson@intel.com, ferruh.yigit@intel.com,
> jasvinder.singh@intel.com
> Subject: [dpdk-dev] [PATCH v3 3/5] common: add missing implementations
> X-Mailer: git-send-email 1.7.0.7
>
> External Email
>
> Implement missing functions for 32-bit safe bsf, as well as 64-bit
> fls and log2.
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> ---
> +/**
> + * Return the last (most-significant) bit set.
> + *
> + * @note The last (most significant) bit is at position 32.
s/position 32/position 64
> + * @note rte_fls_u32(0) = 0, rte_fls_u32(1) = 1, rte_fls_u32(0x80000000) = 32
Fix here too
IMO, it is better to add unit test case for newly added common functions
in test/test/test_common.c
> + *
> + * @param x
> + * The input parameter.
> + * @return
> + * The last (most-significant) bit set, or 0 if the input is 0.
> + */
> +static inline int
> +rte_fls_u64(uint64_t x)
> +{
> + return (x == 0) ? 0 : 64 - __builtin_clzll(x);
> +}
> +
next prev parent reply other threads:[~2018-11-15 8:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 12:11 [PATCH] bitmap: deprecate rte_bsf64 Anatoly Burakov
2018-11-14 16:30 ` [PATCH v2 1/5] bitmap: remove useless code Anatoly Burakov
2018-11-14 16:40 ` Dumitrescu, Cristian
2018-11-14 16:47 ` [PATCH v3 " Anatoly Burakov
2018-11-14 16:47 ` [PATCH v3 2/5] bitmap: rename rte_bsf64 and move to common header Anatoly Burakov
2018-11-14 16:52 ` Singh, Jasvinder
2018-11-22 16:54 ` Hunt, David
2018-11-14 16:47 ` [PATCH v3 3/5] common: add missing implementations Anatoly Burakov
2018-11-15 8:40 ` Jerin Jacob [this message]
2018-11-15 10:07 ` Burakov, Anatoly
2018-11-14 16:47 ` [PATCH v3 4/5] memalloc: use library implementation of 64-bit log2 Anatoly Burakov
2018-11-14 16:47 ` [PATCH v3 5/5] testpmd: " Anatoly Burakov
2018-11-15 10:08 ` [PATCH v2 1/5] bitmap: remove useless code Burakov, Anatoly
2018-11-14 16:30 ` [PATCH v2 2/5] bitmap: rename rte_bsf64 and move to common header Anatoly Burakov
2018-11-14 16:30 ` [PATCH v2 3/5] common: add missing implementations Anatoly Burakov
2018-11-14 16:30 ` [PATCH v2 4/5] memalloc: use library implementation of 64-bit log2 Anatoly Burakov
2018-11-14 16:30 ` [PATCH v2 5/5] testpmd: " Anatoly Burakov
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=20181115083955.GA4757@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jasvinder.singh@intel.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 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.