From: Mel Gorman <mgorman@techsingularity.net>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Tang Chen <tangchen@cn.fujitsu.com>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
"robert.liu@huawei.com" <robert.liu@huawei.com>
Subject: Re: [RFC] mem-hotplug: shall we skip unmovable node when doing numa balance?
Date: Thu, 10 Nov 2016 09:07:22 +0000 [thread overview]
Message-ID: <20161110090722.yyznotwqqxz3v6uo@techsingularity.net> (raw)
In-Reply-To: <5823E6AF.8040600@huawei.com>
On Thu, Nov 10, 2016 at 11:17:03AM +0800, Xishi Qiu wrote:
> On 2016/11/9 19:58, Mel Gorman wrote:
>
> > On Tue, Nov 08, 2016 at 12:43:17PM +0800, Xishi Qiu wrote:
> >> On mem-hotplug system, there is a problem, please see the following case.
> >>
> >> memtester xxG, the memory will be alloced on a movable node. And after numa
> >> balancing, the memory may be migrated to the other node, it may be a unmovable
> >> node. This will reduce the free memory of the unmovable node, and may be oom
> >> later.
> >>
> >
> > How would it OOM later? It's movable memmory that is moving via
> > automatic NUMA balancing so at the very least it can be reclaimed. If
> > the memory is mlocked or unable to migrate then it's irrelevant if
> > automatic balancing put it there.
> >
>
> memtester will mlock the memory, so we can not reclaim, then maybe oom, right?
> So let the manager set some numa policies to prevent the above case, right?
>
Deal with it using policies.
--
Mel Gorman
SUSE Labs
--
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>
prev parent reply other threads:[~2016-11-10 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 4:43 [RFC] mem-hotplug: shall we skip unmovable node when doing numa balance? Xishi Qiu
2016-11-09 11:58 ` Mel Gorman
2016-11-10 3:17 ` Xishi Qiu
2016-11-10 9:07 ` Mel Gorman [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=20161110090722.yyznotwqqxz3v6uo@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qiuxishi@huawei.com \
--cc=robert.liu@huawei.com \
--cc=tangchen@cn.fujitsu.com \
--cc=vbabka@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).