linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Geunsik Lim <geunsik.lim@gmail.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] Handling of unused variable 'do-numainfo on compilation time
Date: Sat, 4 Feb 2012 00:36:36 +0900	[thread overview]
Message-ID: <CAGFP0LK4_PhKLJVtMhsNe4YfUQoHcoTK3hJhHaBy51f359ef7A@mail.gmail.com> (raw)
In-Reply-To: <20120203145304.GA18335@tiehlicka.suse.cz>

[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]

On Fri, Feb 3, 2012 at 11:53 PM, Michal Hocko <mhocko@suse.cz> wrote:

> On Fri 03-02-12 14:39:50, Johannes Weiner wrote:
> > Michal, this keeps coming up, please decide between the proposed
> > solutions ;-)
>
> Hmm, I thought we already sorted this out
> https://lkml.org/lkml/2012/1/26/25 ?
>
> I don't know previous history about this variable.
Is it same? Please, adjust this patch or fix the unsuitable
variable 'do_numainfo' as I mentioned.

> >
> > On Fri, Feb 03, 2012 at 05:43:47PM +0900, Geunsik Lim wrote:
> > > Actually, Usage of the variable 'do_numainfo'is not suitable for gcc
> compiler.
> > > Declare the variable 'do_numainfo' if the number of NUMA nodes > 1.
> > >
> > > Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>
> > > ---
> > >  mm/memcontrol.c |    5 ++++-
> > >  1 files changed, 4 insertions(+), 1 deletions(-)
> > >
> > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > > index 556859f..4e17ac5 100644
> > > --- a/mm/memcontrol.c
> > > +++ b/mm/memcontrol.c
> > > @@ -776,7 +776,10 @@ static void memcg_check_events(struct mem_cgroup
> *memcg, struct page *page)
> > >     /* threshold event is triggered in finer grain than soft limit */
> > >     if (unlikely(mem_cgroup_event_ratelimit(memcg,
> > >
> MEM_CGROUP_TARGET_THRESH))) {
> > > -           bool do_softlimit, do_numainfo;
> > > +           bool do_softlimit;
> > > +#if MAX_NUMNODES > 1
> > > +                bool do_numainfo;
> > > +#endif
> > >
> > >             do_softlimit = mem_cgroup_event_ratelimit(memcg,
> > >
> MEM_CGROUP_TARGET_SOFTLIMIT);
> > > --
> > > 1.7.8.1
> > >
>
> --
> Michal Hocko
> SUSE Labs
> SUSE LINUX s.r.o.
> Lihovarska 1060/12
> 190 00 Praha 9
> Czech Republic
>



-- 
----
Best regards,
Geunsik Lim, Samsung Electronics
http://leemgs.fedorapeople.org
----
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[-- Attachment #2: Type: text/html, Size: 3589 bytes --]

  reply	other threads:[~2012-02-03 15:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03  8:43 Geunsik Lim
2012-02-03 13:39 ` Johannes Weiner
2012-02-03 14:53   ` Michal Hocko
2012-02-03 15:36     ` Geunsik Lim [this message]
2012-02-03 16:04       ` Michal Hocko
2012-02-03 16:06     ` Johannes Weiner

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=CAGFP0LK4_PhKLJVtMhsNe4YfUQoHcoTK3hJhHaBy51f359ef7A@mail.gmail.com \
    --to=geunsik.lim@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=nishimura@mxp.nes.nec.co.jp \
    /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