linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zi Yan <ziy@nvidia.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, "\"Huang,
	Ying\"" <ying.huang@intel.com>,
	Ryan Roberts <ryan.roberts@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"\"Matthew Wilcox (Oracle)\"" <willy@infradead.org>,
	David Hildenbrand <david@redhat.com>,
	"\"Yin, Fengwei\"" <fengwei.yin@intel.com>,
	Yu Zhao <yuzhao@google.com>,
	"\"Kirill A . Shutemov\"" <kirill.shutemov@linux.intel.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Kemeng Shi <shikemeng@huaweicloud.com>,
	Mel Gorman <mgorman@techsingularity.net>,
	Rohan Puri <rohan.puri15@gmail.com>,
	Mcgrof Chamberlain <mcgrof@kernel.org>,
	Adam Manzanares <a.manzanares@samsung.com>,
	"\"Vishal Moola (Oracle)\"" <vishal.moola@gmail.com>
Subject: Re: [PATCH v3 1/3] mm/compaction: enable compacting >0 order folios.
Date: Fri, 09 Feb 2024 14:25:00 -0500	[thread overview]
Message-ID: <24D4AA55-42F5-4E9B-822D-2BE61D0FA51F@nvidia.com> (raw)
In-Reply-To: <c42a6c9f-7d45-428c-95b9-98367ddba9d3@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 5711 bytes --]

On 9 Feb 2024, at 9:32, Vlastimil Babka wrote:

> On 2/2/24 17:15, Zi Yan wrote:
>> From: Zi Yan <ziy@nvidia.com>
>>
>> migrate_pages() supports >0 order folio migration and during compaction,
>> even if compaction_alloc() cannot provide >0 order free pages,
>> migrate_pages() can split the source page and try to migrate the base pages
>> from the split. It can be a baseline and start point for adding support for
>> compacting >0 order folios.
>>
>> Suggested-by: Huang Ying <ying.huang@intel.com>
>> Signed-off-by: Zi Yan <ziy@nvidia.com>
>> ---
>>  mm/compaction.c | 43 +++++++++++++++++++++++++++++++++++--------
>>  1 file changed, 35 insertions(+), 8 deletions(-)
>>
>> diff --git a/mm/compaction.c b/mm/compaction.c
>> index 4add68d40e8d..e43e898d2c77 100644
>> --- a/mm/compaction.c
>> +++ b/mm/compaction.c
>> @@ -816,6 +816,21 @@ static bool too_many_isolated(struct compact_control *cc)
>>  	return too_many;
>>  }
>>
>> +/*
>> + * 1. if the page order is larger than or equal to target_order (i.e.,
>> + * cc->order and when it is not -1 for global compaction), skip it since
>> + * target_order already indicates no free page with larger than target_order
>> + * exists and later migrating it will most likely fail;
>> + *
>> + * 2. compacting > pageblock_order pages does not improve memory fragmentation,
>> + * skip them;
>> + */
>> +static bool skip_isolation_on_order(int order, int target_order)
>> +{
>> +	return (target_order != -1 && order >= target_order) ||
>> +		order >= pageblock_order;
>> +}
>> +
>>  /**
>>   * isolate_migratepages_block() - isolate all migrate-able pages within
>>   *				  a single pageblock
>> @@ -1010,7 +1025,7 @@ isolate_migratepages_block(struct compact_control *cc, unsigned long low_pfn,
>>  		/*
>>  		 * Regardless of being on LRU, compound pages such as THP and
>>  		 * hugetlbfs are not to be compacted unless we are attempting
>> -		 * an allocation much larger than the huge page size (eg CMA).
>> +		 * an allocation larger than the compound page size.
>>  		 * We can potentially save a lot of iterations if we skip them
>>  		 * at once. The check is racy, but we can consider only valid
>>  		 * values and the only danger is skipping too much.
>> @@ -1018,11 +1033,18 @@ isolate_migratepages_block(struct compact_control *cc, unsigned long low_pfn,
>>  		if (PageCompound(page) && !cc->alloc_contig) {
>>  			const unsigned int order = compound_order(page);
>>
>> -			if (likely(order <= MAX_PAGE_ORDER)) {
>> -				low_pfn += (1UL << order) - 1;
>> -				nr_scanned += (1UL << order) - 1;
>> +			/*
>> +			 * Skip based on page order and compaction target order
>> +			 * and skip hugetlbfs pages.
>> +			 */
>> +			if (skip_isolation_on_order(order, cc->order) ||
>> +			    PageHuge(page)) {
>
> Hm I'd try to avoid a new PageHuge() test here.
>
> Earlier we have a block that does
>                 if (PageHuge(page) && cc->alloc_contig) {
> 			...
>
> think I'd rather rewrite it to handle the PageHuge() case completely and
> just make it skip the 1UL << order pages there for !cc->alloc_config. Even
> if it means duplicating a bit of the low_pfn and nr_scanned bumping code.
>
> Which reminds me the PageHuge() check there is probably still broken ATM:
>
> https://lore.kernel.org/all/8fa1c95c-4749-33dd-42ba-243e492ab109@suse.cz/
>
> Even better reason not to add another one.
> If the huge page materialized since the first check, we should bail out when
> testing PageLRU later anyway.


OK, so basically something like:

if (PageHuge(page)) {
    if (cc->alloc_contig) {
        // existing code for PageHuge(page) && cc->allc_contig
    } else {
        const unsigned int order = compound_order(page);

        if (order <= MAX_PAGE_ORDER) {
            low_pfn += (1UL << order) - 1;
            nr_scanned += (1UL << order) - 1;
        }
        goto isolate_fail;
    }
}

...

if (PageCompound(page) && !cc->alloc_contig) {
        const unsigned int order = compound_order(page);

        /* Skip based on page order and compaction target order. */
        if (skip_isolation_on_order(order, cc->order)) {
                if (order <= MAX_PAGE_ORDER) {
                        low_pfn += (1UL << order) - 1;
                        nr_scanned += (1UL << order) - 1;
                }
                goto isolate_fail;
        }
}

>
>> +				if (order <= MAX_PAGE_ORDER) {
>> +					low_pfn += (1UL << order) - 1;
>> +					nr_scanned += (1UL << order) - 1;
>> +				}
>> +				goto isolate_fail;
>>  			}
>> -			goto isolate_fail;
>>  		}
>>
>>  		/*
>> @@ -1165,10 +1187,11 @@ isolate_migratepages_block(struct compact_control *cc, unsigned long low_pfn,
>>  			}
>>
>>  			/*
>> -			 * folio become large since the non-locked check,
>> -			 * and it's on LRU.
>> +			 * Check LRU folio order under the lock
>>  			 */
>> -			if (unlikely(folio_test_large(folio) && !cc->alloc_contig)) {
>> +			if (unlikely(skip_isolation_on_order(folio_order(folio),
>> +							     cc->order) &&
>> +				     !cc->alloc_contig)) {
>>  				low_pfn += folio_nr_pages(folio) - 1;
>>  				nr_scanned += folio_nr_pages(folio) - 1;
>>  				folio_set_lru(folio);
>> @@ -1786,6 +1809,10 @@ static struct folio *compaction_alloc(struct folio *src, unsigned long data)
>>  	struct compact_control *cc = (struct compact_control *)data;
>>  	struct folio *dst;
>>
>> +	/* this makes migrate_pages() split the source page and retry */
>> +	if (folio_test_large(src) > 0)
>> +		return NULL;
>> +
>>  	if (list_empty(&cc->freepages)) {
>>  		isolate_freepages(cc);
>>


--
Best Regards,
Yan, Zi

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]

  reply	other threads:[~2024-02-09 19:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 16:15 [PATCH v3 0/3] Enable >0 order folio memory compaction Zi Yan
2024-02-02 16:15 ` [PATCH v3 1/3] mm/compaction: enable compacting >0 order folios Zi Yan
2024-02-09 14:32   ` Vlastimil Babka
2024-02-09 19:25     ` Zi Yan [this message]
2024-02-09 20:43       ` Vlastimil Babka
2024-02-09 20:44         ` Zi Yan
2024-02-02 16:15 ` [PATCH v3 2/3] mm/compaction: add support for >0 order folio memory compaction Zi Yan
2024-02-09 16:37   ` Vlastimil Babka
2024-02-09 19:36     ` Zi Yan
2024-02-09 19:40       ` Zi Yan
2024-02-09 20:46         ` Vlastimil Babka
2024-02-09 20:47           ` Zi Yan
2024-02-09 21:58     ` Zi Yan
2024-02-02 16:15 ` [PATCH v3 3/3] mm/compaction: optimize >0 order folio compaction with free page split Zi Yan
2024-02-09 18:43   ` Vlastimil Babka
2024-02-09 19:57     ` Zi Yan
2024-02-09 20:49       ` Vlastimil Babka
2024-02-02 19:55 ` [PATCH v3 0/3] Enable >0 order folio memory compaction Luis Chamberlain
2024-02-02 20:12   ` Zi Yan
2024-02-05  8:16 ` Baolin Wang
2024-02-05 14:18   ` 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=24D4AA55-42F5-4E9B-822D-2BE61D0FA51F@nvidia.com \
    --to=ziy@nvidia.com \
    --cc=a.manzanares@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@redhat.com \
    --cc=fengwei.yin@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mcgrof@kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=rohan.puri15@gmail.com \
    --cc=ryan.roberts@arm.com \
    --cc=shikemeng@huaweicloud.com \
    --cc=vbabka@suse.cz \
    --cc=vishal.moola@gmail.com \
    --cc=willy@infradead.org \
    --cc=ying.huang@intel.com \
    --cc=yuzhao@google.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;
as well as URLs for NNTP newsgroup(s).