linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Kiryl Shutsemau <kirill@shutemov.name>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@redhat.com>,
	Hugh Dickins <hughd@google.com>,
	Matthew Wilcox <willy@infradead.org>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>, Rik van Riel <riel@surriel.com>,
	Harry Yoo <harry.yoo@oracle.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Kiryl Shutsemau <kas@kernel.org>
Subject: Re: [PATCHv2 5/5] mm/rmap: Improve mlock tracking for large folios
Date: Mon, 22 Sep 2025 11:20:57 +0800	[thread overview]
Message-ID: <29d9fa8a-5ff2-47f3-8503-fe3032097e5e@linux.alibaba.com> (raw)
In-Reply-To: <20250919124036.455709-6-kirill@shutemov.name>



On 2025/9/19 20:40, Kiryl Shutsemau wrote:
> From: Kiryl Shutsemau <kas@kernel.org>
> 
> The kernel currently does not mlock large folios when adding them to
> rmap, stating that it is difficult to confirm that the folio is fully
> mapped and safe to mlock it.
> 
> This leads to a significant undercount of Mlocked in /proc/meminfo,
> causing problems in production where the stat was used to estimate
> system utilization and determine if load shedding is required.
> 
> However, nowadays the caller passes a number of pages of the folio that
> are getting mapped, making it easy to check if the entire folio is
> mapped to the VMA.
> 
> mlock the folio on rmap if it is fully mapped to the VMA.
> 
> Mlocked in /proc/meminfo can still undercount, but the value is closer
> the truth and is useful for userspace.
> 
> Signed-off-by: Kiryl Shutsemau <kas@kernel.org>
> Acked-by: David Hildenbrand <david@redhat.com>
> Acked-by: Johannes Weiner <hannes@cmpxchg.org>
> Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
> Reviewed-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---

LGTM.
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>

>   mm/rmap.c | 19 ++++++++++++-------
>   1 file changed, 12 insertions(+), 7 deletions(-)
> 
> diff --git a/mm/rmap.c b/mm/rmap.c
> index 482e6504fa88..6e09956670f4 100644
> --- a/mm/rmap.c
> +++ b/mm/rmap.c
> @@ -1462,12 +1462,12 @@ static __always_inline void __folio_add_anon_rmap(struct folio *folio,
>   	}
>   
>   	/*
> -	 * For large folio, only mlock it if it's fully mapped to VMA. It's
> -	 * not easy to check whether the large folio is fully mapped to VMA
> -	 * here. Only mlock normal 4K folio and leave page reclaim to handle
> -	 * large folio.
> +	 * Only mlock it if the folio is fully mapped to the VMA.
> +	 *
> +	 * Partially mapped folios can be split on reclaim and part outside
> +	 * of mlocked VMA can be evicted or freed.
>   	 */
> -	if (!folio_test_large(folio))
> +	if (folio_nr_pages(folio) == nr_pages)
>   		mlock_vma_folio(folio, vma);
>   }
>   
> @@ -1603,8 +1603,13 @@ static __always_inline void __folio_add_file_rmap(struct folio *folio,
>   	nr = __folio_add_rmap(folio, page, nr_pages, vma, level, &nr_pmdmapped);
>   	__folio_mod_stat(folio, nr, nr_pmdmapped);
>   
> -	/* See comments in folio_add_anon_rmap_*() */
> -	if (!folio_test_large(folio))
> +	/*
> +	 * Only mlock it if the folio is fully mapped to the VMA.
> +	 *
> +	 * Partially mapped folios can be split on reclaim and part outside
> +	 * of mlocked VMA can be evicted or freed.
> +	 */
> +	if (folio_nr_pages(folio) == nr_pages)
>   		mlock_vma_folio(folio, vma);
>   }
>   



      reply	other threads:[~2025-09-22  3:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19 12:40 [PATCHv2 0/5] mm: " Kiryl Shutsemau
2025-09-19 12:40 ` [PATCHv2 1/5] mm/page_vma_mapped: Track if the page is mapped across page table boundary Kiryl Shutsemau
2025-09-19 20:25   ` Shakeel Butt
2025-09-22 16:13     ` Kiryl Shutsemau
2025-09-19 12:40 ` [PATCHv2 2/5] mm/rmap: Fix a mlock race condition in folio_referenced_one() Kiryl Shutsemau
2025-09-19 21:18   ` Shakeel Butt
2025-09-19 12:40 ` [PATCHv2 3/5] mm/rmap: mlock large folios in try_to_unmap_one() Kiryl Shutsemau
2025-09-19 21:27   ` Shakeel Butt
2025-09-22  9:51     ` Kiryl Shutsemau
2025-09-22 20:16       ` Shakeel Butt
2025-09-19 12:40 ` [PATCHv2 4/5] mm/fault: Try to map the entire file folio in finish_fault() Kiryl Shutsemau
2025-09-19 21:28   ` Shakeel Butt
2025-09-20  7:37   ` Matthew Wilcox
2025-09-22 16:16     ` Kiryl Shutsemau
2025-09-22  3:19   ` Baolin Wang
2025-09-19 12:40 ` [PATCHv2 5/5] mm/rmap: Improve mlock tracking for large folios Kiryl Shutsemau
2025-09-22  3:20   ` Baolin 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=29d9fa8a-5ff2-47f3-8503-fe3032097e5e@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=harry.yoo@oracle.com \
    --cc=hughd@google.com \
    --cc=kas@kernel.org \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=riel@surriel.com \
    --cc=rppt@kernel.org \
    --cc=shakeel.butt@linux.dev \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --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