From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, ferruh.yigit@intel.com,
Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: [dpdk-dev] [PATCH 1/4] eal: introduce the rte macro for always inline
Date: Sat, 13 May 2017 14:57:25 +0530 [thread overview]
Message-ID: <20170513092728.30050-1-jerin.jacob@caviumnetworks.com> (raw)
Different drivers use internal macros like force_inline for compiler
always inline feature.
Standardizing it through __rte_always_inline macro.
Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
---
This patch has the following false positive checkpatch warning:
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#26: FILE: lib/librte_eal/common/include/rte_common.h:108:
+#define __rte_always_inline inline __attribute__((always_inline))
---
lib/librte_eal/common/include/rte_common.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/lib/librte_eal/common/include/rte_common.h b/lib/librte_eal/common/include/rte_common.h
index e057f6e21..a9a749488 100644
--- a/lib/librte_eal/common/include/rte_common.h
+++ b/lib/librte_eal/common/include/rte_common.h
@@ -102,6 +102,11 @@ typedef uint16_t unaligned_uint16_t;
*/
#define RTE_SET_USED(x) (void)(x)
+/**
+ * Force a function to be inlined
+ */
+#define __rte_always_inline inline __attribute__((always_inline))
+
/*********** Macros for pointer arithmetic ********/
/**
--
2.13.0
next reply other threads:[~2017-05-13 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 9:27 Jerin Jacob [this message]
2017-05-13 9:27 ` [dpdk-dev] [PATCH 2/4] eal: use " Jerin Jacob
2017-05-13 9:27 ` [dpdk-dev] [PATCH 3/4] eal: introduce the rte macro for noinline Jerin Jacob
2017-05-13 9:27 ` [dpdk-dev] [PATCH 4/4] drivers/net: use " Jerin Jacob
2017-05-15 8:07 ` [dpdk-dev] [PATCH 1/4] eal: introduce the rte macro for always inline Bruce Richardson
2017-06-06 20:35 ` Thomas Monjalon
2017-06-01 11:57 ` Bruce Richardson
2017-06-01 11:59 ` Bruce Richardson
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=20170513092728.30050-1-jerin.jacob@caviumnetworks.com \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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 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).