From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andre Wild <wild@linux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Thomas Gleixner <tglx@linutronix.de>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] mm: take memory hotplug lock within numa_zonelist_order_handler()
Date: Wed, 26 Jul 2017 13:48:12 +0200 [thread overview]
Message-ID: <20170726114812.GH3218@osiris> (raw)
In-Reply-To: <20170726113112.GJ2981@dhcp22.suse.cz>
On Wed, Jul 26, 2017 at 01:31:12PM +0200, Michal Hocko wrote:
> On Wed 26-07-17 13:17:38, Heiko Carstens wrote:
> [...]
> > diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> > index 6d30e914afb6..fc32aa81f359 100644
> > --- a/mm/page_alloc.c
> > +++ b/mm/page_alloc.c
> > @@ -4891,9 +4891,11 @@ int numa_zonelist_order_handler(struct ctl_table *table, int write,
> > NUMA_ZONELIST_ORDER_LEN);
> > user_zonelist_order = oldval;
> > } else if (oldval != user_zonelist_order) {
> > + mem_hotplug_begin();
> > mutex_lock(&zonelists_mutex);
> > build_all_zonelists(NULL, NULL);
> > mutex_unlock(&zonelists_mutex);
> > + mem_hotplug_done();
> > }
> > }
> > out:
>
> Please note that this code has been removed by
> http://lkml.kernel.org/r/20170721143915.14161-2-mhocko@kernel.org. It
> will get to linux-next as soon as Andrew releases a new version mmotm
> tree.
We still would need something for 4.13, no?
--
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: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andre Wild <wild@linux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Thomas Gleixner <tglx@linutronix.de>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] mm: take memory hotplug lock within numa_zonelist_order_handler()
Date: Wed, 26 Jul 2017 13:48:12 +0200 [thread overview]
Message-ID: <20170726114812.GH3218@osiris> (raw)
In-Reply-To: <20170726113112.GJ2981@dhcp22.suse.cz>
On Wed, Jul 26, 2017 at 01:31:12PM +0200, Michal Hocko wrote:
> On Wed 26-07-17 13:17:38, Heiko Carstens wrote:
> [...]
> > diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> > index 6d30e914afb6..fc32aa81f359 100644
> > --- a/mm/page_alloc.c
> > +++ b/mm/page_alloc.c
> > @@ -4891,9 +4891,11 @@ int numa_zonelist_order_handler(struct ctl_table *table, int write,
> > NUMA_ZONELIST_ORDER_LEN);
> > user_zonelist_order = oldval;
> > } else if (oldval != user_zonelist_order) {
> > + mem_hotplug_begin();
> > mutex_lock(&zonelists_mutex);
> > build_all_zonelists(NULL, NULL);
> > mutex_unlock(&zonelists_mutex);
> > + mem_hotplug_done();
> > }
> > }
> > out:
>
> Please note that this code has been removed by
> http://lkml.kernel.org/r/20170721143915.14161-2-mhocko@kernel.org. It
> will get to linux-next as soon as Andrew releases a new version mmotm
> tree.
We still would need something for 4.13, no?
next prev parent reply other threads:[~2017-07-26 11:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 11:17 [PATCH] mm: take memory hotplug lock within numa_zonelist_order_handler() Heiko Carstens
2017-07-26 11:17 ` Heiko Carstens
2017-07-26 11:31 ` Michal Hocko
2017-07-26 11:31 ` Michal Hocko
2017-07-26 11:48 ` Heiko Carstens [this message]
2017-07-26 11:48 ` Heiko Carstens
2017-07-26 12:19 ` Michal Hocko
2017-07-26 12:19 ` Michal Hocko
2017-07-26 22:25 ` Andrew Morton
2017-07-26 22:25 ` Andrew Morton
2017-07-27 6:54 ` Michal Hocko
2017-07-27 6:54 ` Michal Hocko
2017-07-26 13:34 ` Thomas Gleixner
2017-07-26 13:34 ` Thomas Gleixner
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=20170726114812.GH3218@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=wild@linux.vnet.ibm.com \
/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.