linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sidhartha Kumar <sidhartha.kumar@oracle.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	akpm@linux-foundation.org, songmuchun@bytedance.com,
	willy@infradead.org, almasrymina@google.com,
	linmiaohe@huawei.com, minhquangbui99@gmail.com,
	aneesh.kumar@linux.ibm.com
Subject: Re: [PATCH 3/9] mm/hugetlb_cgroup: convert set_hugetlb_cgroup*() to folios
Date: Tue, 1 Nov 2022 09:43:11 -0700	[thread overview]
Message-ID: <139d4fe5-c77e-f90a-2b7e-ac2798f4e118@oracle.com> (raw)
In-Reply-To: <Y1/5+R7H4yub8epq@monkey>



On 10/31/22 9:38 AM, Mike Kravetz wrote:
> On 10/13/22 20:12, Sidhartha Kumar wrote:
>> Allows __prep_new_huge_page() to operate on a folio by converting
>> set_hugetlb_cgroup*() to take in a folio.
>>
>> Signed-off-by: Sidhartha Kumar <sidhartha.kumar@oracle.com>
>> --- a/mm/hugetlb.c
>> +++ b/mm/hugetlb.c
>> @@ -1758,19 +1758,21 @@ static void __prep_account_new_huge_page(struct hstate *h, int nid)
>>   	h->nr_huge_pages_node[nid]++;
>>   }
>>   
>> -static void __prep_new_huge_page(struct hstate *h, struct page *page)
>> +static void __prep_new_hugetlb_folio(struct hstate *h, struct folio *folio)
>>   {
>> -	hugetlb_vmemmap_optimize(h, page);
>> -	INIT_LIST_HEAD(&page->lru);
>> -	set_compound_page_dtor(page, HUGETLB_PAGE_DTOR);
>> -	hugetlb_set_page_subpool(page, NULL);
>> -	set_hugetlb_cgroup(page, NULL);
>> -	set_hugetlb_cgroup_rsvd(page, NULL);
>> +	hugetlb_vmemmap_optimize(h, &folio->page);
>> +	INIT_LIST_HEAD(&folio->lru);
>> +	folio->_folio_dtor = HUGETLB_PAGE_DTOR;
> Seems like we should have a routine 'set_folio_dtor' that has the same
> functionality as set_compound_page_dtor.  Here, we loose the check for a
> valid DTOR value (although not terribly valuable).

I agree with the need for a 'set_folio_dtor' routine, I'll send out a 
patch for that as well.

> Not required for this patch, but something to note.
>
>> +	hugetlb_set_folio_subpool(folio, NULL);
>> +	set_hugetlb_cgroup(folio, NULL);
>> +	set_hugetlb_cgroup_rsvd(folio, NULL);
>>   }
>>   
>>   static void prep_new_huge_page(struct hstate *h, struct page *page, int nid)
>>   {
>> -	__prep_new_huge_page(h, page);
>> +	struct folio *folio = page_folio(page);
>> +
>> +	__prep_new_hugetlb_folio(h, folio);
>>   	spin_lock_irq(&hugetlb_lock);
>>   	__prep_account_new_huge_page(h, nid);
>>   	spin_unlock_irq(&hugetlb_lock);
>> @@ -2731,8 +2733,10 @@ static int alloc_and_dissolve_huge_page(struct hstate *h, struct page *old_page,
>>   					struct list_head *list)
>>   {
>>   	gfp_t gfp_mask = htlb_alloc_mask(h) | __GFP_THISNODE;
>> -	int nid = page_to_nid(old_page);
>> +	struct folio *old_folio = page_folio(old_page);
>> +	int nid = folio_nid(old_folio);
>>   	struct page *new_page;
>> +	struct folio *new_folio;
>>   	int ret = 0;
>>   
>>   	/*
>> @@ -2745,16 +2749,17 @@ static int alloc_and_dissolve_huge_page(struct hstate *h, struct page *old_page,
>>   	new_page = alloc_buddy_huge_page(h, gfp_mask, nid, NULL, NULL);
>>   	if (!new_page)
>>   		return -ENOMEM;
>> -	__prep_new_huge_page(h, new_page);
>> +	new_folio = page_folio(new_page);
>> +	__prep_new_hugetlb_folio(h, new_folio);
>>   
>>   retry:
>>   	spin_lock_irq(&hugetlb_lock);
>> -	if (!PageHuge(old_page)) {
>> +	if (!folio_test_hugetlb(old_folio)) {
>>   		/*
>>   		 * Freed from under us. Drop new_page too.
>>   		 */
>>   		goto free_new;
>> -	} else if (page_count(old_page)) {
>> +	} else if (folio_ref_count(old_folio)) {
>>   		/*
>>   		 * Someone has grabbed the page, try to isolate it here.
>>   		 * Fail with -EBUSY if not possible.
>> @@ -2763,7 +2768,7 @@ static int alloc_and_dissolve_huge_page(struct hstate *h, struct page *old_page,
>>   		ret = isolate_hugetlb(old_page, list);
>>   		spin_lock_irq(&hugetlb_lock);
>>   		goto free_new;
>> -	} else if (!HPageFreed(old_page)) {
>> +	} else if (!folio_test_hugetlb(old_folio)) {
> Should that be?
> 	} else if (!folio_test_hugetlb_freed(old_folio)) {

Yes good catch, I will fix in a v2.

Thanks,
Sidhartha Kumar

>


  reply	other threads:[~2022-11-01 16:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  3:12 [PATCH 0/9] convert hugetlb_cgroup helper functions to folios Sidhartha Kumar
2022-10-14  3:12 ` [PATCH 1/9] mm/hugetlb_cgroup: convert __set_hugetlb_cgroup() " Sidhartha Kumar
2022-10-31 14:51   ` Mike Kravetz
2022-10-14  3:12 ` [PATCH 2/9] mm/hugetlb_cgroup: convert hugetlb_cgroup_from_page() " Sidhartha Kumar
2022-10-31 16:13   ` Mike Kravetz
2022-11-01 16:40     ` Sidhartha Kumar
2022-10-14  3:12 ` [PATCH 3/9] mm/hugetlb_cgroup: convert set_hugetlb_cgroup*() " Sidhartha Kumar
2022-10-31 16:38   ` Mike Kravetz
2022-11-01 16:43     ` Sidhartha Kumar [this message]
2022-10-14  3:12 ` [PATCH 4/9] mm/hugetlb_cgroup: convert hugetlb_cgroup_migrate " Sidhartha Kumar
2022-10-31 16:50   ` Mike Kravetz
2022-10-14  3:12 ` [PATCH 5/9] mm/hugetlb: convert isolate_or_dissolve_huge_page " Sidhartha Kumar
2022-10-31 19:37   ` Mike Kravetz
2022-10-14  3:13 ` [PATCH 6/9] mm/hugetlb: convert free_huge_page " Sidhartha Kumar
2022-10-17 20:36   ` Andrew Morton
2022-10-31 19:44   ` Mike Kravetz
2022-10-14  3:13 ` [PATCH 7/9] mm/hugetlb_cgroup: convert hugetlb_cgroup_uncharge_page() " Sidhartha Kumar
2022-10-31 20:11   ` Mike Kravetz
2022-10-14  3:13 ` [PATCH 8/9] mm/hugeltb_cgroup: convert hugetlb_cgroup_commit_charge*() " Sidhartha Kumar
2022-10-31 20:22   ` Mike Kravetz
2022-10-14  3:13 ` [PATCH 9/9] mm/hugetlb: convert move_hugetlb_state() " Sidhartha Kumar
2022-10-31 20:56   ` Mike Kravetz

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=139d4fe5-c77e-f90a-2b7e-ac2798f4e118@oracle.com \
    --to=sidhartha.kumar@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=almasrymina@google.com \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=minhquangbui99@gmail.com \
    --cc=songmuchun@bytedance.com \
    --cc=willy@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).