From: Michal Hocko <mhocko@kernel.org>
To: Li Xinhai <lixinhai.lxh@gmail.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: Re: [PATCH v4] mm/page_vma_mapped.c: Explicitly compare pfn for normal, hugetlbfs and THP page
Date: Tue, 14 Jan 2020 10:25:45 +0100 [thread overview]
Message-ID: <20200114092545.GF19428@dhcp22.suse.cz> (raw)
In-Reply-To: <1578737885-8890-1-git-send-email-lixinhai.lxh@gmail.com>
On Sat 11-01-20 10:18:05, Li Xinhai wrote:
> When check_pte, pfn of normal, hugetlbfs and THP page need be compared.
> The current implementation apply comparison as
> - normal 4K page: page_pfn <= pfn < page_pfn + 1
> - hugetlbfs page: page_pfn <= pfn < page_pfn + HPAGE_PMD_NR
> - THP page: page_pfn <= pfn < page_pfn + HPAGE_PMD_NR
> in pfn_in_hpage. For hugetlbfs page, it should be
> page_pfn == pfn
>
> Now, change pfn_in_hpage to pfn_is_match to highlight that comparison
> is not only for THP and explicitly compare for these cases.
Why is this important to do. I have asked and Mike had the same feeling
that the patch is missing any real justification. Why do we need this
change? It is great that you have dropped VM_BUG_ON btw.
> Signed-off-by: Li Xinhai <lixinhai.lxh@gmail.com>
> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Cc: Mike Kravetz <mike.kravetz@oracle.com>
> Cc: Michal Hocko <mhocko@kernel.org>
> Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> ---
> mm/page_vma_mapped.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/mm/page_vma_mapped.c b/mm/page_vma_mapped.c
> index eff4b45..719c352 100644
> --- a/mm/page_vma_mapped.c
> +++ b/mm/page_vma_mapped.c
> @@ -52,12 +52,16 @@ static bool map_pte(struct page_vma_mapped_walk *pvmw)
> return true;
> }
>
> -static inline bool pfn_in_hpage(struct page *hpage, unsigned long pfn)
> +static inline bool pfn_is_match(struct page *page, unsigned long pfn)
> {
> - unsigned long hpage_pfn = page_to_pfn(hpage);
> + unsigned long page_pfn = page_to_pfn(page);
> +
> + /* normal page and hugetlbfs page */
> + if (!PageTransCompound(page) || PageHuge(page))
> + return page_pfn == pfn;
>
> /* THP can be referenced by any subpage */
> - return pfn >= hpage_pfn && pfn - hpage_pfn < hpage_nr_pages(hpage);
> + return pfn >= page_pfn && pfn - page_pfn < hpage_nr_pages(page);
> }
>
> /**
> @@ -108,7 +112,7 @@ static bool check_pte(struct page_vma_mapped_walk *pvmw)
> pfn = pte_pfn(*pvmw->pte);
> }
>
> - return pfn_in_hpage(pvmw->page, pfn);
> + return pfn_is_match(pvmw->page, pfn);
> }
>
> /**
> --
> 1.8.3.1
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-01-14 9:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 10:18 Li Xinhai
2020-01-13 22:38 ` Andrew Morton
2020-01-14 14:24 ` Li Xinhai
2020-01-14 9:25 ` Michal Hocko [this message]
2020-01-14 13:47 ` Li Xinhai
2020-01-15 9:31 ` Michal Hocko
2020-01-16 0:40 ` Mike Kravetz
2020-01-16 10:29 ` Michal Hocko
2020-09-02 22:26 ` Yang Shi
2020-09-03 8:02 ` Michal Hocko
2020-09-03 16:08 ` Yang Shi
2020-09-04 1:22 ` Yang Shi
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=20200114092545.GF19428@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=lixinhai.lxh@gmail.com \
--cc=mike.kravetz@oracle.com \
/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