From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Support for __read_mostly
Date: Sun, 5 Dec 2010 11:42:57 +0000 [thread overview]
Message-ID: <20101205114257.GD9138@n2100.arm.linux.org.uk> (raw)
This patch set adds support for __read_mostly - a separate section
which is used to hold data which is hardly ever written.
The idea behind this feature is to reduce the amount of cache line
bouncing between SMP cores by avoiding this data sharing cache lines
with data which is written more frequently. As long as a cache line
is not dirtied, several cores can keep a copy of the data in their
caches.
next reply other threads:[~2010-12-05 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 11:42 Russell King - ARM Linux [this message]
2010-12-05 11:43 ` [PATCH 1/2] ARM: implement support for read-mostly sections Russell King - ARM Linux
2010-12-05 22:18 ` Catalin Marinas
2010-12-05 23:04 ` Russell King - ARM Linux
2010-12-06 17:51 ` Catalin Marinas
2010-12-05 11:43 ` [PATCH 2/2] ARM: move high-usage mostly read variables in setup.c to __read_mostly Russell King - ARM Linux
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=20101205114257.GD9138@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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).