linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>, Barry Song <21cnbao@gmail.com>
Cc: akpm@linux-foundation.org, hughd@google.com, willy@infradead.org,
	david@redhat.com, ryan.roberts@arm.com, ziy@nvidia.com,
	gshan@redhat.com, ioworker0@gmail.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mm: shmem: avoid allocating huge pages larger than MAX_PAGECACHE_ORDER for shmem
Date: Wed, 31 Jul 2024 18:22:17 +0800	[thread overview]
Message-ID: <ba3e3dfa-d019-4991-9e3a-d73ffa83bb36@linux.alibaba.com> (raw)
In-Reply-To: <87769ae8-b6c6-4454-925d-1864364af9c8@huawei.com>



On 2024/7/31 17:59, Kefeng Wang wrote:
> 
> 
> On 2024/7/31 16:56, Baolin Wang wrote:
>>
>>
>> On 2024/7/31 14:18, Barry Song wrote:
>>> On Wed, Jul 31, 2024 at 1:46 PM Baolin Wang
>>> <baolin.wang@linux.alibaba.com> wrote:
>>>>
>>>> Similar to commit d659b715e94ac ("mm/huge_memory: avoid PMD-size 
>>>> page cache
>>>> if needed"), ARM64 can support 512MB PMD-sized THP when the base 
>>>> page size is
>>>> 64KB, which is larger than the maximum supported page cache size 
>>>> MAX_PAGECACHE_ORDER.
>>>> This is not expected. To fix this issue, use 
>>>> THP_ORDERS_ALL_FILE_DEFAULT for
>>>> shmem to filter allowable huge orders.
>>>>
>>>> Fixes: e7a2ab7b3bb5 ("mm: shmem: add mTHP support for anonymous shmem")
>>>> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>>>
>>> Reviewed-by: Barry Song <baohua@kernel.org>
>>
>> Thanks for reviewing.
>>
>>>
>>>> ---
>>>>   mm/shmem.c | 4 ++--
>>>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/mm/shmem.c b/mm/shmem.c
>>>> index 2faa9daaf54b..a4332a97558c 100644
>>>> --- a/mm/shmem.c
>>>> +++ b/mm/shmem.c
>>>> @@ -1630,10 +1630,10 @@ unsigned long 
>>>> shmem_allowable_huge_orders(struct inode *inode,
>>>>          unsigned long within_size_orders = 
>>>> READ_ONCE(huge_shmem_orders_within_size);
>>>>          unsigned long vm_flags = vma->vm_flags;
>>>>          /*
>>>> -        * Check all the (large) orders below HPAGE_PMD_ORDER + 1 that
>>>> +        * Check all the (large) orders below MAX_PAGECACHE_ORDER + 
>>>> 1 that
>>>>           * are enabled for this vma.
>>>
>>> Nit:
>>> THP_ORDERS_ALL_FILE_DEFAULT should be self-explanatory enough.
>>> I feel we don't need this comment?
>>
>> Sure.
>>
>> Andrew, please help to squash the following changes into this patch. 
>> Thanks.
> 
> Maybe drop unsigned long orders too?
> 
> diff --git a/mm/shmem.c b/mm/shmem.c
> index 6af95f595d6f..8485eb6f2ec4 100644
> --- a/mm/shmem.c
> +++ b/mm/shmem.c
> @@ -1638,11 +1638,6 @@ unsigned long shmem_allowable_huge_orders(struct 
> inode *inode,
>          unsigned long mask = READ_ONCE(huge_shmem_orders_always);
>          unsigned long within_size_orders = 
> READ_ONCE(huge_shmem_orders_within_size);
>          unsigned long vm_flags = vma ? vma->vm_flags : 0;
> -       /*
> -        * Check all the (large) orders below HPAGE_PMD_ORDER + 1 that
> -        * are enabled for this vma.
> -        */
> -       unsigned long orders = BIT(PMD_ORDER + 1) - 1;
>          bool global_huge;
>          loff_t i_size;
>          int order;
> @@ -1698,7 +1693,7 @@ unsigned long shmem_allowable_huge_orders(struct 
> inode *inode,
>          if (global_huge)
>                  mask |= READ_ONCE(huge_shmem_orders_inherit);
> 
> -       return orders & mask;
> +       return THP_ORDERS_ALL_FILE_DEFAULT & mask;
>   }

Yes. Good point. Thanks.
(Hope Andrew can help to squash these changes :))


  reply	other threads:[~2024-07-31 10:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31  5:46 Baolin Wang
2024-07-31  5:46 ` [PATCH 2/2] mm: shmem: fix incorrect aligned index when checking conflicts Baolin Wang
2024-07-31  9:18   ` David Hildenbrand
2024-07-31  6:18 ` [PATCH 1/2] mm: shmem: avoid allocating huge pages larger than MAX_PAGECACHE_ORDER for shmem Barry Song
2024-07-31  8:56   ` Baolin Wang
2024-07-31  9:59     ` Kefeng Wang
2024-07-31 10:22       ` Baolin Wang [this message]
2024-07-31 20:48         ` Andrew Morton
2024-08-01  0:06           ` Baolin Wang
2024-08-01 19:55             ` Andrew Morton
2024-08-02  3:11               ` Baolin Wang
2024-07-31  9:17 ` David Hildenbrand
2024-07-31 13:09 ` Zi Yan

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=ba3e3dfa-d019-4991-9e3a-d73ffa83bb36@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=gshan@redhat.com \
    --cc=hughd@google.com \
    --cc=ioworker0@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ryan.roberts@arm.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=willy@infradead.org \
    --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