From: Michal Hocko <mhocko@suse.com>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/mempolicy: clean up the code logic in queue_pages_pte_range
Date: Fri, 22 Apr 2022 13:48:00 +0200 [thread overview]
Message-ID: <YmKV8ESXIPFBR2mj@dhcp22.suse.cz> (raw)
In-Reply-To: <20220419122234.45083-1-linmiaohe@huawei.com>
On Tue 19-04-22 20:22:34, Miaohe Lin wrote:
> Since commit e5947d23edd8 ("mm: mempolicy: don't have to split pmd for
> huge zero page"), THP is never splited in queue_pages_pmd. Thus 2 is
> never returned now. We can remove such unnecessary ret != 2 check and
> clean up the relevant comment. Minor improvements in readability.
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Thanks!
> ---
> mm/mempolicy.c | 12 +++---------
> 1 file changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/mm/mempolicy.c b/mm/mempolicy.c
> index 75a8b247f631..3934476fb708 100644
> --- a/mm/mempolicy.c
> +++ b/mm/mempolicy.c
> @@ -441,12 +441,11 @@ static inline bool queue_pages_required(struct page *page,
> }
>
> /*
> - * queue_pages_pmd() has four possible return values:
> + * queue_pages_pmd() has three possible return values:
> * 0 - pages are placed on the right node or queued successfully, or
> * special page is met, i.e. huge zero page.
> * 1 - there is unmovable page, and MPOL_MF_MOVE* & MPOL_MF_STRICT were
> * specified.
> - * 2 - THP was split.
> * -EIO - is migration entry or only MPOL_MF_STRICT was specified and an
> * existing page was already on a node that does not follow the
> * policy.
> @@ -508,18 +507,13 @@ static int queue_pages_pte_range(pmd_t *pmd, unsigned long addr,
> struct page *page;
> struct queue_pages *qp = walk->private;
> unsigned long flags = qp->flags;
> - int ret;
> bool has_unmovable = false;
> pte_t *pte, *mapped_pte;
> spinlock_t *ptl;
>
> ptl = pmd_trans_huge_lock(pmd, vma);
> - if (ptl) {
> - ret = queue_pages_pmd(pmd, ptl, addr, end, walk);
> - if (ret != 2)
> - return ret;
> - }
> - /* THP was split, fall through to pte walk */
> + if (ptl)
> + return queue_pages_pmd(pmd, ptl, addr, end, walk);
>
> if (pmd_trans_unstable(pmd))
> return 0;
> --
> 2.23.0
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2022-04-22 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 12:22 Miaohe Lin
2022-04-21 0:44 ` Yang Shi
2022-04-22 11:48 ` Michal Hocko [this message]
2022-04-24 19:23 ` 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=YmKV8ESXIPFBR2mj@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.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