linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: Khalid Aziz <khalid.aziz@oracle.com>
Cc: David Hildenbrand <david@redhat.com>,
	 akpm@linux-foundation.org, willy@infradead.org,
	 steven.sistare@oracle.com, mgorman@techsingularity.net,
	 khalid@kernel.org,  linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] mm, compaction: Skip all non-migratable pages during scan
Date: Tue, 23 May 2023 09:23:25 +0800	[thread overview]
Message-ID: <87bkibyh6a.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <5ba66714-b4a9-4fd3-1149-4d67b26c370a@oracle.com> (Khalid Aziz's message of "Mon, 22 May 2023 09:12:38 -0600")

Khalid Aziz <khalid.aziz@oracle.com> writes:

> On 5/21/23 23:55, Huang, Ying wrote:
>> David Hildenbrand <david@redhat.com> writes:
>> 
>>> On 18.05.23 03:09, Huang, Ying wrote:
>>>> David Hildenbrand <david@redhat.com> writes:
>>>>
>>>>> On 17.05.23 18:15, Khalid Aziz wrote:
>>>>>> Pages pinned in memory through extra refcounts can not be migrated.
>>>>>> Currently as isolate_migratepages_block() scans pages for
>>>>>> compaction, it skips any pinned anonymous pages. All non-migratable
>>>>>> pages should be skipped and not just the anonymous pinned pages.
>>>>>> This patch adds a check for extra refcounts on a page to determine
>>>>>> if the page can be migrated.  This was seen as a real issue on a
>>>>>> customer workload where a large number of pages were pinned by vfio
>>>>>> on the host and any attempts to allocate hugepages resulted in
>>>>>> significant amount of cpu time spent in either direct compaction or
>>>>>> in kcompactd scanning vfio pinned pages over and over again that can
>>>>>> not be migrated.
>>>>>
>>>>> How will this change affect alloc_contig_range(), such as used for CMA
>>>>> allocations or virtio-mem? alloc_contig_range() ends up calling
>>>>> isolate_migratepages_range() -> isolate_migratepages_block().
>>>> IIUC, cc->alloc_contig can be used to distinguish contiguous
>>>> allocation
>>>> and compaction.  And, from the original commit which introduced
>>>> anonymous pages skipping (commit 119d6d59dcc0 ("mm, compaction: avoid
>>>> isolating pinned pages ")) and this patch, large number of migration
>>>> failure during compaction causes real issue too.  So, I suggest to use
>>>> cc->alloc_contig here.
>>>
>>> Agreed. I further wonder if we want to special-case the !alloc_contig
>>> case also for MIGRATE_CMA and ZONE_MOVABLE, where we cannot have
>>> longterm page pinnings (e.g., vfio pinned pages).
>> This makes sense.  The skipping is more accurate in this way.
>> 
>
>
> Something like this?
>
> diff --git a/mm/compaction.c b/mm/compaction.c
> index f04c00981172..014e21d3d7e9 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -1025,7 +1025,7 @@ isolate_migratepages_block(struct compact_control *cc, unsigned long low_pfn,
>                  * lru_lock and isolating it unnecessarily
>                  */
>                 mapping = page_mapping(page);
> -               if (page_has_extra_refs(page))
> +               if (!cc->alloc_contig && page_has_extra_refs(page))
>                         goto isolate_fail_put;
>
>                 /*

As suggested by David above, you can check the current zone type (for
ZONE_MOVABLE) and page block migrate type (MIGRATE_CMA) too.  Because
pages there will not be pinned in long term, and should be tried to be
migrated.

Best Regards,
Huang, Ying


  reply	other threads:[~2023-05-23  1:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 16:15 Khalid Aziz
2023-05-17 18:32 ` David Hildenbrand
2023-05-17 22:33   ` Khalid Aziz
2023-05-18  1:09   ` Huang, Ying
2023-05-19  9:51     ` David Hildenbrand
2023-05-22  5:55       ` Huang, Ying
2023-05-22 15:12         ` Khalid Aziz
2023-05-23  1:23           ` Huang, Ying [this message]
2023-05-18  1:21 ` Huang, Ying
2023-05-18 15:07   ` Khalid Aziz
2023-05-19  0:19     ` Huang, Ying
2023-05-23  3:42 ` Baolin Wang
2023-05-23 20:54   ` Khalid Aziz

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=87bkibyh6a.fsf@yhuang6-desk2.ccr.corp.intel.com \
    --to=ying.huang@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=khalid.aziz@oracle.com \
    --cc=khalid@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=steven.sistare@oracle.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