From: Michal Hocko <mhocko@kernel.org>
To: changbin.du@intel.com
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] mm, thp: introduce generic transparent huge page allocation interfaces
Date: Fri, 8 Dec 2017 09:27:37 +0100 [thread overview]
Message-ID: <20171208082737.GA15790@dhcp22.suse.cz> (raw)
In-Reply-To: <1512708175-14089-1-git-send-email-changbin.du@intel.com>
On Fri 08-12-17 12:42:55, changbin.du@intel.com wrote:
> From: Changbin Du <changbin.du@intel.com>
>
> This patch introduced 4 new interfaces to allocate a prepared transparent
> huge page. These interfaces merge distributed two-step allocation as simple
> single step. And they can avoid issue like forget to call prep_transhuge_page()
> or call it on wrong page. A real fix:
> 40a899e ("mm: migrate: fix an incorrect call of prep_transhuge_page()")
>
> Anyway, I just want to prove that expose direct allocation interfaces is
> better than a interface only do the second part of it.
>
> These are similar to alloc_hugepage_xxx which are for hugetlbfs pages. New
> interfaces are:
> - alloc_transhuge_page_vma
> - alloc_transhuge_page_nodemask
> - alloc_transhuge_page_node
> - alloc_transhuge_page
>
> These interfaces implicitly add __GFP_COMP gfp mask which is the minimum
> flags used for huge page allocation. More flags leave to the callers.
>
> This patch does below changes:
> - define alloc_transhuge_page_xxx interfaces
> - apply them to all existing code
> - declare prep_transhuge_page as static since no others use it
> - remove alloc_hugepage_vma definition since it no longer has users
I am not really convinced this is a huge win, to be honest. Just look at
the diffstat. Very few callsites get marginally simpler while we add a
lot of stubs and the code churn.
> Signed-off-by: Changbin Du <changbin.du@intel.com>
>
> ---
> v4:
> - Revise the nop function definition. (Andrew)
>
> v3:
> - Rebase to latest mainline.
>
> v2:
> Anshuman Khandu:
> - Remove redundant 'VM_BUG_ON(!(gfp_mask & __GFP_COMP))'.
> Andrew Morton:
> - Fix build error if thp is disabled.
> ---
> include/linux/gfp.h | 4 ----
> include/linux/huge_mm.h | 35 +++++++++++++++++++++++++++++++++--
> include/linux/migrate.h | 14 +++++---------
> mm/huge_memory.c | 48 +++++++++++++++++++++++++++++++++++++++++-------
> mm/khugepaged.c | 11 ++---------
> mm/mempolicy.c | 14 +++-----------
> mm/migrate.c | 14 ++++----------
> mm/shmem.c | 6 ++----
> 8 files changed, 90 insertions(+), 56 deletions(-)
--
Michal Hocko
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>
next prev parent reply other threads:[~2017-12-08 8:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 4:42 changbin.du
2017-12-08 8:27 ` Michal Hocko [this message]
2017-12-09 3:26 ` Du, Changbin
2017-12-10 9:55 ` Michal Hocko
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=20171208082737.GA15790@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=changbin.du@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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