All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Russ Anderson <rja@sgi.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com
Subject: Re: [patch] mm: speedup in __early_pfn_to_nid
Date: Fri, 22 Mar 2013 08:25:32 +0100	[thread overview]
Message-ID: <20130322072532.GC10608@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1303211139110.3775@chino.kir.corp.google.com>


* David Rientjes <rientjes@google.com> wrote:

> On Thu, 21 Mar 2013, Ingo Molnar wrote:
> 
> > > Index: linux/mm/page_alloc.c
> > > ===================================================================
> > > --- linux.orig/mm/page_alloc.c	2013-03-18 10:52:11.510988843 -0500
> > > +++ linux/mm/page_alloc.c	2013-03-18 10:52:14.214931348 -0500
> > > @@ -4161,10 +4161,19 @@ int __meminit __early_pfn_to_nid(unsigne
> > >  {
> > >  	unsigned long start_pfn, end_pfn;
> > >  	int i, nid;
> > > +	static unsigned long last_start_pfn, last_end_pfn;
> > > +	static int last_nid;
> > 
> > Please move these globals out of function local scope, to make it more 
> > apparent that they are not on-stack. I only noticed it in the second pass.
> 
> The way they're currently defined places these in meminit.data as 
> appropriate; if they are moved out, please make sure to annotate their 
> definitions with __meminitdata.

I'm fine with having them within the function as well in this special 
case, as long as a heavy /* NOTE: ... */ warning is put before them - 
which explains why these SMP-unsafe globals are safe.

( That warning will also act as a visual delimiter that breaks the 
  normally confusing and misleading 'globals mixed amongst stack 
  variables' pattern. )

Thanks,

	Ingo

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Russ Anderson <rja@sgi.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com
Subject: Re: [patch] mm: speedup in __early_pfn_to_nid
Date: Fri, 22 Mar 2013 08:25:32 +0100	[thread overview]
Message-ID: <20130322072532.GC10608@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1303211139110.3775@chino.kir.corp.google.com>


* David Rientjes <rientjes@google.com> wrote:

> On Thu, 21 Mar 2013, Ingo Molnar wrote:
> 
> > > Index: linux/mm/page_alloc.c
> > > ===================================================================
> > > --- linux.orig/mm/page_alloc.c	2013-03-18 10:52:11.510988843 -0500
> > > +++ linux/mm/page_alloc.c	2013-03-18 10:52:14.214931348 -0500
> > > @@ -4161,10 +4161,19 @@ int __meminit __early_pfn_to_nid(unsigne
> > >  {
> > >  	unsigned long start_pfn, end_pfn;
> > >  	int i, nid;
> > > +	static unsigned long last_start_pfn, last_end_pfn;
> > > +	static int last_nid;
> > 
> > Please move these globals out of function local scope, to make it more 
> > apparent that they are not on-stack. I only noticed it in the second pass.
> 
> The way they're currently defined places these in meminit.data as 
> appropriate; if they are moved out, please make sure to annotate their 
> definitions with __meminitdata.

I'm fine with having them within the function as well in this special 
case, as long as a heavy /* NOTE: ... */ warning is put before them - 
which explains why these SMP-unsafe globals are safe.

( That warning will also act as a visual delimiter that breaks the 
  normally confusing and misleading 'globals mixed amongst stack 
  variables' pattern. )

Thanks,

	Ingo

  reply	other threads:[~2013-03-22  7:25 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 15:56 [patch] mm: speedup in __early_pfn_to_nid Russ Anderson
2013-03-18 15:56 ` Russ Anderson
2013-03-19  3:56 ` David Rientjes
2013-03-19  3:56   ` David Rientjes
2013-03-20 22:32 ` Andrew Morton
2013-03-20 22:32   ` Andrew Morton
2013-03-20 22:32   ` Andrew Morton
2013-03-21 10:55 ` Ingo Molnar
2013-03-21 10:55   ` Ingo Molnar
2013-03-21 12:35   ` Michal Hocko
2013-03-21 12:35     ` Michal Hocko
2013-03-21 18:03     ` Ingo Molnar
2013-03-21 18:03       ` Ingo Molnar
2013-03-25 21:26       ` Andrew Morton
2013-03-25 21:26         ` Andrew Morton
2013-03-26  8:05         ` Ingo Molnar
2013-03-26  8:05           ` Ingo Molnar
2013-03-21 18:40   ` David Rientjes
2013-03-21 18:40     ` David Rientjes
2013-03-22  7:25     ` Ingo Molnar [this message]
2013-03-22  7:25       ` Ingo Molnar
2013-03-23 15:29       ` Russ Anderson
2013-03-23 15:29         ` Russ Anderson
2013-03-23 20:37         ` Yinghai Lu
2013-03-25  2:11           ` Lin Feng
2013-03-25  2:11             ` Lin Feng
2013-03-25 21:56             ` Russ Anderson
2013-03-25 21:56               ` Russ Anderson
2013-03-25 22:17               ` Yinghai Lu
2013-03-23 22:24         ` KOSAKI Motohiro
2013-03-23 22:24           ` KOSAKI Motohiro
2013-03-25  0:28           ` David Rientjes
2013-03-25  0:28             ` David Rientjes
2013-03-25 21:34             ` Andrew Morton
2013-03-25 21:34               ` Andrew Morton
2013-03-25 22:36               ` David Rientjes
2013-03-25 22:36                 ` David Rientjes
2013-03-25 22:42                 ` Andrew Morton
2013-03-25 22:42                   ` Andrew Morton
2013-03-24  7:43         ` Ingo Molnar
2013-03-24  7:43           ` Ingo Molnar

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=20130322072532.GC10608@gmail.com \
    --to=mingo@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=rientjes@google.com \
    --cc=rja@sgi.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.