linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Michal Hocko <mhocko@suse.cz>,
	linux-mm@kvack.org, kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [PATCH] hugeltb: Mark hugelb_max_hstate __read_mostly
Date: Fri, 22 Jun 2012 15:03:02 -0700	[thread overview]
Message-ID: <20120622150302.f0e349e4.akpm@linux-foundation.org> (raw)
In-Reply-To: <87pq91m7fz.fsf@skywalker.in.ibm.com>

On Fri, 15 Jun 2012 11:40:24 +0530
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> wrote:

> Michal Hocko <mhocko@suse.cz> writes:
> 
> > On Thu 14-06-12 19:26:18, Aneesh Kumar K.V wrote:
> >> From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
> >> 
> >> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> >> ---
> >>  include/linux/hugetlb.h |    2 +-
> >>  mm/hugetlb.c            |    2 +-
> >>  2 files changed, 2 insertions(+), 2 deletions(-)
> >> 
> >> diff --git a/include/linux/hugetlb.h b/include/linux/hugetlb.h
> >> index 9650bb1..0f0877e 100644
> >> --- a/include/linux/hugetlb.h
> >> +++ b/include/linux/hugetlb.h
> >> @@ -23,7 +23,7 @@ struct hugepage_subpool {
> >>  };
> >>  
> >>  extern spinlock_t hugetlb_lock;
> >> -extern int hugetlb_max_hstate;
> >> +extern int hugetlb_max_hstate __read_mostly;
> >
> > It should be used only for definition
> >
> I looked at the rest of the source and found multiple place where we
> specify __read_mostly in extern.
> 
> arch/x86/kernel/cpu/perf_event.h extern struct x86_pmu x86_pmu __read_mostly;

We have had one situation in the past where the lack of a section
annotation on a declaration caused an architecture (arm?) to fail to
build.  iirc the compiler emitted some short-mode relative-addressed
opcode to reference the variable, but when the linker came along to
resolve the offset it discovered that it exceeded the short-mode
addressing range, because that variable was in a section which landed
far away from .data.

That's only happened once, and that architecture might have changed,
and we're missing the section annotation on many variables anyway, so
I'd be inclined to just leave it off - if we ever hit significant
problems with this, we have a lot of work to do.

Also, we currently have no automated way of keeping the annotation on
the declaration and definition in sync.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2012-06-22 22:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 13:56 [PATCH] hugeltb: Mark hugelb_max_hstate __read_mostly Aneesh Kumar K.V
2012-06-14 14:12 ` Michal Hocko
2012-06-14 20:43   ` Christoph Lameter
2012-06-15  6:08     ` Aneesh Kumar K.V
2012-06-15 13:57       ` Christoph Lameter
2012-06-15 14:33         ` Michal Hocko
2012-06-15 14:50           ` Christoph Lameter
2012-06-22 22:06             ` Andrew Morton
2012-06-15  6:10   ` Aneesh Kumar K.V
2012-06-22 22:03     ` Andrew Morton [this message]

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=20120622150302.f0e349e4.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    /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).