From: Michal Hocko <mhocko@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
ying.huang@intel.com, s.priebe@profihost.ag,
mgorman@techsingularity.net,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
alex.williamson@redhat.com, lkp@01.org, kirill@shutemov.name,
Andrew Morton <akpm@linux-foundation.org>,
zi.yan@cs.rutgers.edu, Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [patch 1/2 for-4.20] mm, thp: restore node-local hugepage allocations
Date: Wed, 5 Dec 2018 21:15:28 +0100 [thread overview]
Message-ID: <20181205201528.GW1286@dhcp22.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.21.1812051120550.240991@chino.kir.corp.google.com>
On Wed 05-12-18 11:24:53, David Rientjes wrote:
> On Wed, 5 Dec 2018, Michal Hocko wrote:
>
> > > > At minimum do not remove the cleanup part which consolidates the gfp
> > > > hadnling to a single place. There is no real reason to have the
> > > > __GFP_THISNODE ugliness outside of alloc_hugepage_direct_gfpmask.
> > > >
> > >
> > > The __GFP_THISNODE usage is still confined to
> > > alloc_hugepage_direct_gfpmask() for the thp fault path, we no longer set
> > > it in alloc_pages_vma() as done before the cleanup.
> >
> > Why should be new_page any different?
> >
>
> To match alloc_new_node_page() which does it correctly and does not change
> the behavior of mbind() that the cleanup did, which used
> alloc_hugepage_vma() to get the __GFP_THISNODE behavior. If there is a
> reason mbind() is somehow different wrt allocating hugepages locally, I
> think that should be a separate patch, but the goal of this patch is to
> revert all the behavioral change that caused hugepages to be allocated
> remotely.
If the __GFP_THISNODE should be really used then it should be applied to
all other types of pages. Not only THP. And as such done in a separate
patch. Not a part of the revert. The cleanup was meant to unify THP
allocations and that is why I object to reverting it as a part of this
work.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-12-05 20:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 23:50 [patch 0/2 for-4.20] mm, thp: fix remote access and allocation regressions David Rientjes
2018-12-03 23:50 ` [patch 2/2 for-4.20] mm, thp: always fault memory with __GFP_NORETRY David Rientjes
2018-12-03 23:50 ` [patch 1/2 for-4.20] mm, thp: restore node-local hugepage allocations David Rientjes
2018-12-04 7:35 ` Michal Hocko
2018-12-04 21:56 ` David Rientjes
2018-12-05 7:34 ` Michal Hocko
2018-12-05 19:24 ` David Rientjes
2018-12-05 20:15 ` Michal Hocko [this message]
2018-12-05 22:21 ` Andrea Arcangeli
2018-12-04 7:38 ` [patch 0/2 for-4.20] mm, thp: fix remote access and allocation regressions Michal Hocko
2018-12-04 22:25 ` David Rientjes
2018-12-05 7:40 ` Michal Hocko
2018-12-05 10:15 ` Mel Gorman
2018-12-05 19:41 ` David Rientjes
2018-12-04 10:10 ` Vlastimil Babka
2018-12-04 22:04 ` David Rientjes
2018-12-05 9:05 ` Michal Hocko
2018-12-05 19:49 ` David Rientjes
2018-12-05 20:32 ` Michal Hocko
2018-12-05 21:14 ` David Rientjes
2018-12-05 21:45 ` Andrea Arcangeli
2018-12-05 22:10 ` David Rientjes
2018-12-06 0:31 ` Andrea Arcangeli
2018-12-09 22:44 ` David Rientjes
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=20181205201528.GW1286@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mgorman@techsingularity.net \
--cc=rientjes@google.com \
--cc=s.priebe@profihost.ag \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=ying.huang@intel.com \
--cc=zi.yan@cs.rutgers.edu \
/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
all inboxes | Powered by JetHome®