From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
To: thomas@monjalon.net, jerin.jacob@caviumnetworks.com, techboard@dpdk.org
Cc: dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Subject: [dpdk-dev] [PATCH 1/2] eal: add macro to mark variable mostly read only
Date: Wed, 18 Apr 2018 21:00:34 +0530 [thread overview]
Message-ID: <20180418153035.5972-1-pbhagavatula@caviumnetworks.com> (raw)
Add macro to mark a variable to be mostly read only and place it in a
separate section.
Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
---
Group together mostly read only data to avoid cacheline bouncing, also
useful for auditing purposes.
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 6c5bc5a76..f2ff2e9e6 100644
--- a/lib/librte_eal/common/include/rte_common.h
+++ b/lib/librte_eal/common/include/rte_common.h
@@ -114,6 +114,11 @@ static void __attribute__((constructor(prio), used)) func(void)
*/
#define __rte_noinline __attribute__((noinline))
+/**
+ * Mark a variable to be mostly read only and place it in a separate section.
+ */
+#define __rte_read_mostly __attribute__((__section__(".read_mostly")))
+
/*********** Macros for pointer arithmetic ********/
/**
--
2.17.0
next reply other threads:[~2018-04-18 15:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 15:30 Pavan Nikhilesh [this message]
2018-04-18 15:30 ` [dpdk-dev] [PATCH 2/2] drivers: mark logtype variables as read mostly Pavan Nikhilesh
2018-04-18 17:43 ` [dpdk-dev] [PATCH 1/2] eal: add macro to mark variable mostly read only Ferruh Yigit
2018-04-18 17:55 ` Pavan Nikhilesh
2018-04-18 18:03 ` Ferruh Yigit
2018-04-19 9:20 ` Pavan Nikhilesh
2018-04-19 12:09 ` Bruce Richardson
2018-04-19 15:18 ` Pavan Nikhilesh
2018-04-19 15:37 ` Bruce Richardson
2018-04-19 15:55 ` Pavan Nikhilesh
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=20180418153035.5972-1-pbhagavatula@caviumnetworks.com \
--to=pbhagavatula@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=techboard@dpdk.org \
--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).