From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: "pbhagavatula@marvell.com" <pbhagavatula@marvell.com>,
"jerinj@marvell.com" <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [RFC] eal/arm: remove CASP constraints for GCC
Date: Mon, 18 Oct 2021 06:39:15 +0000 [thread overview]
Message-ID: <AS8PR08MB70803AD7587B26B1B97F49529EBC9@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20211004100304.13602-1-pbhagavatula@marvell.com>
> -----Original Message-----
> From: pbhagavatula@marvell.com <pbhagavatula@marvell.com>
> Sent: Monday, October 4, 2021 6:03 PM
> To: jerinj@marvell.com; Ruifeng Wang <Ruifeng.Wang@arm.com>
> Cc: dev@dpdk.org; Pavan Nikhilesh <pbhagavatula@marvell.com>
> Subject: [dpdk-dev] [RFC] eal/arm: remove CASP constraints for GCC
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> GCC now assigns even register pairs for CASP, the fix has also been
> backported to all stable releases of older GCC versions.
> Removing the manual register allocation allows GCC to inline the functions
> and pick optimal registers for performing CASP.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
> lib/eal/arm/include/rte_atomic_64.h | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/lib/eal/arm/include/rte_atomic_64.h
> b/lib/eal/arm/include/rte_atomic_64.h
> index fa6f334c0d..f6f31ae777 100644
> --- a/lib/eal/arm/include/rte_atomic_64.h
> +++ b/lib/eal/arm/include/rte_atomic_64.h
> @@ -52,6 +52,7 @@ rte_atomic_thread_fence(int memorder)
> #define __LSE_PREAMBLE ""
> #endif
>
> +#if defined(__clang__)
> #define __ATOMIC128_CAS_OP(cas_op_name, op_string) \
> static __rte_noinline void \
> cas_op_name(rte_int128_t *dst, rte_int128_t *old, rte_int128_t updated)
> \
> @@ -76,6 +77,19 @@ cas_op_name(rte_int128_t *dst, rte_int128_t *old,
> rte_int128_t updated) \
> old->val[0] = x0; \
> old->val[1] = x1; \
> }
> +#else
> +#define __ATOMIC128_CAS_OP(cas_op_name, op_string) \
> +static __rte_always_inline void \
> +cas_op_name(rte_int128_t *dst, rte_int128_t *old, rte_int128_t updated)
> \
> +{ \
> + asm volatile( \
> + __LSE_PREAMBLE \
Change looks good.
One minor comment, gcc doesn't need this PREAMBLE.
Thanks,
Ruifeng
> + op_string " %[old], %H[old], %[upd], %H[upd], [%[dst]]" \
> + : [old] "+r"(old->int128) \
> + : [upd] "r"(updated.int128), [dst] "r"(dst) \
> + : "memory"); \
> +}
> +#endif
>
> __ATOMIC128_CAS_OP(__cas_128_relaxed, "casp")
> __ATOMIC128_CAS_OP(__cas_128_acquire, "caspa")
> --
> 2.17.1
next prev parent reply other threads:[~2021-10-18 6:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 10:03 pbhagavatula
2021-10-18 6:39 ` Ruifeng Wang [this message]
2021-11-05 8:57 ` [dpdk-dev] [PATCH v2] " pbhagavatula
2021-11-08 7:15 ` Ruifeng Wang
2021-11-16 14:56 ` David Marchand
2022-01-20 15:32 ` [EXT] " Pavan Nikhilesh Bhagavatula
2022-02-11 7:53 ` 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=AS8PR08MB70803AD7587B26B1B97F49529EBC9@AS8PR08MB7080.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=pbhagavatula@marvell.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).