From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
To: dev@dpdk.org, honnappa.nagarahalli@arm.com, jerinj@marvell.com,
hemant.agrawal@nxp.com, akhil.goyal@nxp.com,
ogerlitz@mellanox.com, ajit.khaparde@broadcom.com,
pbhagavatula@marvell.com
Cc: nd@arm.com
Subject: [dpdk-dev] [PATCH v2 2/2] eal/arm: change inline functions to always inline
Date: Fri, 26 Jun 2020 15:35:02 -0500 [thread overview]
Message-ID: <20200626203502.20658-2-honnappa.nagarahalli@arm.com> (raw)
In-Reply-To: <20200626203502.20658-1-honnappa.nagarahalli@arm.com>
Change the inline functions to use __rte_always_inline to be
consistent with rest of the inline functions.
Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
---
lib/librte_eal/arm/include/rte_cycles_64.h | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/lib/librte_eal/arm/include/rte_cycles_64.h b/lib/librte_eal/arm/include/rte_cycles_64.h
index e41f9dbd6..029fdc435 100644
--- a/lib/librte_eal/arm/include/rte_cycles_64.h
+++ b/lib/librte_eal/arm/include/rte_cycles_64.h
@@ -50,7 +50,7 @@ __rte_arm64_cntvct_precise(void)
* This call is portable to any ARMv8 architecture, however, typically
* cntvct_el0 runs at <= 100MHz and it may be imprecise for some tasks.
*/
-static inline uint64_t
+static __rte_always_inline uint64_t
rte_rdtsc(void)
{
return __rte_arm64_cntvct();
@@ -85,22 +85,25 @@ __rte_arm64_pmccntr(void)
return tsc;
}
-static inline uint64_t
+static __rte_always_inline uint64_t
rte_rdtsc(void)
{
return __rte_arm64_pmccntr();
}
#endif
-static inline uint64_t
+static __rte_always_inline uint64_t
rte_rdtsc_precise(void)
{
asm volatile("isb" : : : "memory");
return rte_rdtsc();
}
-static inline uint64_t
-rte_get_tsc_cycles(void) { return rte_rdtsc(); }
+static __rte_always_inline uint64_t
+rte_get_tsc_cycles(void)
+{
+ return rte_rdtsc();
+}
#ifdef __cplusplus
}
--
2.17.1
next prev parent reply other threads:[~2020-06-26 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 21:34 [dpdk-dev] [PATCH] eal: generic counter based loop for CPU freq calculation Honnappa Nagarahalli
2020-06-24 12:50 ` Jerin Jacob
2020-06-26 20:46 ` Honnappa Nagarahalli
2020-06-24 15:09 ` Pavan Nikhilesh Bhagavatula
2020-06-26 20:35 ` [dpdk-dev] [PATCH v2 1/2] eal/arm: " Honnappa Nagarahalli
2020-06-26 20:35 ` Honnappa Nagarahalli [this message]
2020-07-07 2:05 ` [dpdk-dev] [PATCH v2 2/2] eal/arm: change inline functions to always inline Jerin Jacob
2020-07-07 11:16 ` [dpdk-dev] [PATCH v2 1/2] eal/arm: generic counter based loop for CPU freq calculation 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=20200626203502.20658-2-honnappa.nagarahalli@arm.com \
--to=honnappa.nagarahalli@arm.com \
--cc=ajit.khaparde@broadcom.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=ogerlitz@mellanox.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).