linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
	Matthew Wilcox <willy@infradead.org>,
	Muchun Song <muchun.song@linux.dev>,
	"Huang, Ying" <ying.huang@intel.com>,
	Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH 1/2] mm: always use base address when clear gigantic page
Date: Fri, 25 Oct 2024 08:41:38 +0800	[thread overview]
Message-ID: <6a3640b3-20f1-4d98-8e82-5a98b2d64930@huawei.com> (raw)
In-Reply-To: <58f6a052-8b0a-4c1b-88c5-d3a462acc0af@huawei.com>



On 2024/10/24 20:45, Kefeng Wang wrote:
> +cc maillist

Please ignore this series, sorry for the noise, let me resend all
patches with correct cc list.

> 
> On 2024/10/24 20:44, Kefeng Wang wrote:
>> When clear gigantic page, it zeros page from the first subpage to
>> the last subpage, that is, aligned base address is needed in it,
>> and we don't need to aligned down the address in the caller as the
>> real address will be passed to process_huge_page().
>>
>> Fixes: 78fefd04c123 ("mm: memory: convert clear_huge_page() to 
>> folio_zero_user()")
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>>   fs/hugetlbfs/inode.c | 2 +-
>>   mm/memory.c          | 1 +
>>   2 files changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
>> index a4441fb77f7c..a5ea006f403e 100644
>> --- a/fs/hugetlbfs/inode.c
>> +++ b/fs/hugetlbfs/inode.c
>> @@ -825,7 +825,7 @@ static long hugetlbfs_fallocate(struct file *file, 
>> int mode, loff_t offset,
>>               error = PTR_ERR(folio);
>>               goto out;
>>           }
>> -        folio_zero_user(folio, ALIGN_DOWN(addr, hpage_size));
>> +        folio_zero_user(folio, addr);
>>           __folio_mark_uptodate(folio);
>>           error = hugetlb_add_to_page_cache(folio, mapping, index);
>>           if (unlikely(error)) {
>> diff --git a/mm/memory.c b/mm/memory.c
>> index 48e534aa939c..934ab5fff537 100644
>> --- a/mm/memory.c
>> +++ b/mm/memory.c
>> @@ -6802,6 +6802,7 @@ static void clear_gigantic_page(struct folio 
>> *folio, unsigned long addr,
>>       int i;
>>       might_sleep();
>> +    addr = ALIGN_DOWN(addr, folio_size(folio));
>>       for (i = 0; i < nr_pages; i++) {
>>           cond_resched();
>>           clear_user_highpage(folio_page(folio, i), addr + i * 
>> PAGE_SIZE);
> 
> 



      reply	other threads:[~2024-10-25  0:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241024124436.3419497-1-wangkefeng.wang@huawei.com>
2024-10-24 12:45 ` Kefeng Wang
2024-10-25  0:41   ` Kefeng Wang [this message]

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=6a3640b3-20f1-4d98-8e82-5a98b2d64930@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=willy@infradead.org \
    --cc=ying.huang@intel.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