From: Andrea Reale <ar@linux.vnet.ibm.com>
To: Zi Yan <zi.yan@cs.rutgers.edu>
Cc: linux-kernel@vger.kernel.org, n-horiguchi@ah.jp.nec.com,
akpm@linux-foundation.org, jglisse@redhat.com,
realean2@ie.ibm.com
Subject: Re: [PATCH 1/1] mm/migrate: do not call prep_transhuge_page if !thp_migration_supported
Date: Mon, 20 Nov 2017 17:07:09 +0000 [thread overview]
Message-ID: <20171120170708.GB6912@samekh> (raw)
In-Reply-To: <A78EEB02-579C-4CA1-B6CF-C06E4AF6EE22@cs.rutgers.edu>
Hi Yan Zi,
thanks for the feedback. Yes, it looks definitely less redundant :)
Regards,
Andrea
On Mon, Nov 20, 2017 at 11:33:06AM -0500, Zi Yan wrote:
> Hi Andrea,
>
> Thanks for pointing this out.
>
> I think the problem is that we should not prep_transhuge_page(new_page)
> unless new_page is allocated and PageTransHuge(). And several lines above,
> the allocation flags and the order is changed to make new_page a THP
> only if thp_migration_supported() is true.
>
> Does the patch below look better?
>
> diff --git a/include/linux/migrate.h b/include/linux/migrate.h
> index 895ec0c..725eac5 100644
> --- a/include/linux/migrate.h
> +++ b/include/linux/migrate.h
> @@ -54,7 +54,7 @@ static inline struct page *new_page_nodemask(struct page *page,
> new_page = __alloc_pages_nodemask(gfp_mask, order,
> preferred_nid, nodemask);
>
> - if (new_page && PageTransHuge(page))
> + if (new_page && PageTransHuge(new_page))
> prep_transhuge_page(new_page);
>
> return new_page;
> --
>
>
> --
> Best Regards
> Yan Zi
>
> On 20 Nov 2017, at 11:17, Andrea Reale wrote:
>
> > new_page_nodemask in linux/migrate.h should not call prep_transhuge_page
> > if thp_migration_support is false.
> >
> > Fixes commit 8135d8926c08 ("mm: memory_hotplug: memory hotremove supports
> > thp migration")
> >
> > Signed-off-by: Andrea Reale <ar@linux.vnet.ibm.com>
> > ---
> > include/linux/migrate.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/linux/migrate.h b/include/linux/migrate.h
> > index 895ec0c..725eac5 100644
> > --- a/include/linux/migrate.h
> > +++ b/include/linux/migrate.h
> > @@ -54,7 +54,7 @@ static inline struct page *new_page_nodemask(struct page *page,
> > new_page = __alloc_pages_nodemask(gfp_mask, order,
> > preferred_nid, nodemask);
> >
> > - if (new_page && PageTransHuge(page))
> > + if (thp_migration_supported() && new_page && PageTransHuge(page))
> > prep_transhuge_page(new_page);
> >
> > return new_page;
> > --
> > 2.7.4
prev parent reply other threads:[~2017-11-20 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 16:17 [PATCH 0/1] mm/migrate: do not call prep_transhuge_page if !thp_migration_supported Andrea Reale
2017-11-20 16:17 ` [PATCH 1/1] " Andrea Reale
2017-11-20 16:33 ` Zi Yan
2017-11-20 17:07 ` Andrea Reale [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=20171120170708.GB6912@samekh \
--to=ar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=realean2@ie.ibm.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 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.