From: Andrew Morton <akpm@linux-foundation.org>
To: "Jan Beulich" <JBeulich@suse.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] consolidate WARN_...ONCE() static variables
Date: Mon, 27 Feb 2012 16:03:02 -0800 [thread overview]
Message-ID: <20120227160302.ef9f6af4.akpm@linux-foundation.org> (raw)
In-Reply-To: <4F4BAAFA0200007800074F8F@nat28.tlf.novell.com>
On Mon, 27 Feb 2012 15:10:34 +0000
"Jan Beulich" <JBeulich@suse.com> wrote:
> Due to the alignment of following variables, these typically consume
> more than just the single byte that 'bool' requires, and as there are
> a few hundred instances, the cache pollution (not so much the waste of
> memory) sums up. Put these variables into their own section, outside
> of any half way frequently used memory range.
>
> v2: Do the same also to the __warned variable of rcu_lockdep_assert().
> (Don't, however, include the ones used by printk_once() and alike, as
> they can potentially be hot.)
I have a bad feeling that I still don't understand this patch. Ho hum.
What are the rules for the new .data.unlikely section? When should
people put variables into this section? Perhaps we can document this
somewhere?
next prev parent reply other threads:[~2012-02-28 0:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 15:10 [PATCH v2] consolidate WARN_...ONCE() static variables Jan Beulich
2012-02-28 0:03 ` Andrew Morton [this message]
2012-02-28 7:41 ` Jan Beulich
2012-02-28 7:44 ` Andrew Morton
2012-02-28 8:02 ` Jan Beulich
2012-02-28 8:12 ` Andrew Morton
2012-02-28 8:16 ` Jan Beulich
2012-02-28 8:32 ` Andrew Morton
2012-02-28 8:58 ` Jan Beulich
2012-02-28 21:19 ` Andrew Morton
2012-02-29 8:21 ` Jan Beulich
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=20120227160302.ef9f6af4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=JBeulich@suse.com \
--cc=linux-kernel@vger.kernel.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).