From: Peter Xu <peterx@redhat.com>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: akpm@linux-foundation.org, ziy@nvidia.com, willy@infradead.org,
william.kucharski@oracle.com, vbabka@suse.cz,
yulei.kernel@gmail.com, walken@google.com,
aneesh.kumar@linux.ibm.com, rcampbell@nvidia.com,
thomas_os@shipmail.org, yang.shi@linux.alibaba.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 1/6] mm/huge_memory.c: rework the function vma_adjust_trans_huge()
Date: Wed, 17 Mar 2021 09:07:06 -0400 [thread overview]
Message-ID: <20210317130706.GJ395976@xz-x1> (raw)
In-Reply-To: <f4bc08ee-36a0-0018-251b-16399a3182ad@huawei.com>
On Wed, Mar 17, 2021 at 10:18:40AM +0800, Miaohe Lin wrote:
> Hi:
> On 2021/3/17 4:40, Peter Xu wrote:
> > On Tue, Mar 16, 2021 at 08:40:02AM -0400, Miaohe Lin wrote:
> >> +static inline void split_huge_pmd_if_needed(struct vm_area_struct *vma, unsigned long address)
> >> +{
> >> + /*
> >> + * If the new address isn't hpage aligned and it could previously
> >> + * contain an hugepage: check if we need to split an huge pmd.
> >> + */
> >> + if (address & ~HPAGE_PMD_MASK &&
> >> + range_in_vma(vma, address & HPAGE_PMD_MASK,
> >> + (address & HPAGE_PMD_MASK) + HPAGE_PMD_SIZE))
> >
> > Since you're at it, maybe use ALIGN/ALIGN_DOWN too against HPAGE_PMD_SIZE?
> >
>
> Many thanks for reply. Sounds good. :) Do you mean this?
>
> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> index bff92dea5ab3..ae16a82da823 100644
> --- a/mm/huge_memory.c
> +++ b/mm/huge_memory.c
> @@ -2301,44 +2301,38 @@ void split_huge_pmd_address(struct vm_area_struct *vma, unsigned long address,
> __split_huge_pmd(vma, pmd, address, freeze, page);
> }
>
> +static inline void split_huge_pmd_if_needed(struct vm_area_struct *vma, unsigned long address)
> +{
> + /*
> + * If the new address isn't hpage aligned and it could previously
> + * contain an hugepage: check if we need to split an huge pmd.
> + */
> + if (!IS_ALIGNED(address, HPAGE_PMD_SIZE) &&
> + range_in_vma(vma, ALIGN_DOWN(address, HPAGE_PMD_SIZE),
> + ALIGN(address, HPAGE_PMD_SIZE)))
> + split_huge_pmd_address(vma, address, false, NULL);
> +}
> +
Yes. Thanks,
--
Peter Xu
next prev parent reply other threads:[~2021-03-17 13:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 12:40 [PATCH v2 0/6] Some cleanups for huge_memory Miaohe Lin
2021-03-16 12:40 ` [PATCH v2 1/6] mm/huge_memory.c: rework the function vma_adjust_trans_huge() Miaohe Lin
2021-03-16 20:40 ` Peter Xu
2021-03-17 2:18 ` Miaohe Lin
2021-03-17 13:07 ` Peter Xu [this message]
2021-03-16 12:40 ` [PATCH v2 2/6] mm/huge_memory.c: make get_huge_zero_page() return bool Miaohe Lin
2021-03-16 12:40 ` [PATCH v2 3/6] mm/huge_memory.c: rework the function do_huge_pmd_numa_page() slightly Miaohe Lin
2021-03-16 12:40 ` [PATCH v2 4/6] mm/huge_memory.c: remove redundant PageCompound() check Miaohe Lin
2021-03-16 12:40 ` [PATCH v2 5/6] mm/huge_memory.c: remove unused macro TRANSPARENT_HUGEPAGE_DEBUG_COW_FLAG Miaohe Lin
2021-03-16 12:40 ` [PATCH v2 6/6] mm/huge_memory.c: use helper function migration_entry_to_page() Miaohe Lin
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=20210317130706.GJ395976@xz-x1 \
--to=peterx@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rcampbell@nvidia.com \
--cc=thomas_os@shipmail.org \
--cc=vbabka@suse.cz \
--cc=walken@google.com \
--cc=william.kucharski@oracle.com \
--cc=willy@infradead.org \
--cc=yang.shi@linux.alibaba.com \
--cc=yulei.kernel@gmail.com \
--cc=ziy@nvidia.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