From: "Bang Li" <libang.li@antgroup.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>,
ughd@google.com, akpm@linux-foundation.org
Cc: david@redhat.com, ryan.roberts@arm.com,
wangkefeng.wang@huawei.com, ioworker0@gmail.com, ziy@nvidia.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2] mm: thp: support "THPeligible" semantics for mTHP with anonymous shmem
Date: Wed, 03 Jul 2024 15:31:52 +0800 [thread overview]
Message-ID: <c0cbe1c6-1009-4dba-acd1-5b8a1bb1141c@antgroup.com> (raw)
In-Reply-To: <6f383c8c-b125-4374-bf21-67b6cc3edcbe@linux.alibaba.com>
Hi Baolin,
On 2024/7/2 14:14, Baolin Wang wrote:
>
>
> On 2024/7/2 10:34, Bang Li wrote:
>> After the commit 7fb1b252afb5 ("mm: shmem: add mTHP support for
>> anonymous shmem"), we can configure different policies through
>> the multi-size THP sysfs interface for anonymous shmem. But
>> currently "THPeligible" indicates only whether the mapping is
>> eligible for allocating THP-pages as well as the THP is PMD
>> mappable or not for anonymous shmem, we need to support semantics
>> for mTHP with anonymous shmem similar to those for mTHP with
>> anonymous memory.
>>
>> Signed-off-by: Bang Li <libang.li@antgroup.com>
>> ---
>> Changes since v1 [1]:
>> - Put anonymous shmem mthp related logic into
>> thp_vma_allowable_orders() (per David)
>>
>> [1]
>> https://lore.kernel.org/linux-mm/20240628104926.34209-1-libang.li@antgroup.com/
>> ---
>> include/linux/huge_mm.h | 11 +++++++++++
>> mm/huge_memory.c | 13 +++++++++----
>> mm/shmem.c | 9 +--------
>> 3 files changed, 21 insertions(+), 12 deletions(-)
>>
>> diff --git a/include/linux/huge_mm.h b/include/linux/huge_mm.h
>> index 212cca384d7e..f87136f38aa1 100644
>> --- a/include/linux/huge_mm.h
>> +++ b/include/linux/huge_mm.h
>> @@ -267,6 +267,10 @@ unsigned long thp_vma_allowable_orders(struct
>> vm_area_struct *vma,
>> return __thp_vma_allowable_orders(vma, vm_flags, tva_flags,
>> orders);
>> }
>> +unsigned long shmem_allowable_huge_orders(struct inode *inode,
>> + struct vm_area_struct *vma, pgoff_t index,
>> + bool global_huge);
>> +
>> struct thpsize {
>> struct kobject kobj;
>> struct list_head node;
>> @@ -460,6 +464,13 @@ static inline unsigned long
>> thp_vma_allowable_orders(struct vm_area_struct *vma,
>> return 0;
>> }
>> +static inline unsigned long shmem_allowable_huge_orders(struct inode
>> *inode,
>> + struct vm_area_struct *vma, pgoff_t index,
>> + bool global_huge)
>> +{
>> + return 0;
>> +}
>
> This function should be placed in the ‘shmem_fs.h’ header file, just
> like shmem_is_huge().
Looks more reasonable,thank you for your review.
Thanks,
Bang
next prev parent reply other threads:[~2024-07-03 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 2:34 Bang Li
2024-07-02 6:14 ` Baolin Wang
2024-07-03 7:31 ` Bang Li [this message]
2024-07-02 8:18 ` Ryan Roberts
2024-07-03 7:33 ` Bang Li
2024-07-03 10:25 ` Ryan Roberts
2024-07-03 16:02 ` Bang Li
2024-07-04 9:46 ` Ryan Roberts
2024-07-04 10:05 ` Bang Li
2024-07-04 10:25 ` Ryan Roberts
2024-07-04 12:03 ` Bang Li
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=c0cbe1c6-1009-4dba-acd1-5b8a1bb1141c@antgroup.com \
--to=libang.li@antgroup.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=ioworker0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=ughd@google.com \
--cc=wangkefeng.wang@huawei.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