From: Andrew Morton <akpm@linux-foundation.org>
To: Zhiguo Jiang <justinjiang@vivo.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
oe-lkp@lists.linux.dev, lkp@intel.com,
opensource.kernel@vivo.com
Subject: Re: [PATCH v2] vma remove the unneeded avc bound with non-CoWed folio
Date: Fri, 23 Aug 2024 22:35:59 -0700 [thread overview]
Message-ID: <20240823223559.942b53cea16d5cfc6b70bf2d@linux-foundation.org> (raw)
In-Reply-To: <20240823150206.565-1-justinjiang@vivo.com>
On Fri, 23 Aug 2024 23:02:06 +0800 Zhiguo Jiang <justinjiang@vivo.com> wrote:
> After CoWed by do_wp_page, the vma established a new mapping relationship
> with the CoWed folio instead of the non-CoWed folio. However, regarding
> the situation where vma->anon_vma and the non-CoWed folio's anon_vma are
> not same, the avc binding relationship between them will no longer be
> needed, so it is issue for the avc binding relationship still existing
> between them.
>
> This patch will remove the avc binding relationship between vma and the
> non-CoWed folio's anon_vma, which each has their own independent
> anon_vma. It can also alleviates rmap overhead simultaneously.
I assume any performance benefits are unmeasurable?
I'll queue it for testing and shall await reviewer input.
> --- a/mm/rmap.c
> +++ b/mm/rmap.c
> @@ -1522,6 +1522,59 @@ void folio_add_file_rmap_pmd(struct folio *folio, struct page *page,
> #endif
> }
>
> +/**
> + * folio_remove_anon_avc - remove the avc binding relationship between
> + * folio and vma with different anon_vmas.
> + * @folio: The folio with anon_vma to remove the binded avc from
> + * @vma: The vm area to remove the binded avc with folio's anon_vma
> + *
> + * The caller is currently used for CoWed scene.
> + */
> +void folio_remove_anon_avc(struct folio *folio,
> + struct vm_area_struct *vma)
> +{
>
> ...
>
In mm-unstable a lot of vma functions have been moved into the new file
mm/vma.c. I suspect folio_remove_anon_avc() should be there also?
next prev parent reply other threads:[~2024-08-24 5:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 15:02 Zhiguo Jiang
2024-08-24 5:35 ` Andrew Morton [this message]
2024-08-25 4:10 ` zhiguojiang
2024-08-25 4:17 ` zhiguojiang
2024-08-24 16:26 ` Lorenzo Stoakes
2024-08-24 18:04 ` Lorenzo Stoakes
2024-08-25 5:06 ` zhiguojiang
2024-08-25 6:39 ` Lorenzo Stoakes
2024-08-25 18:13 ` Mika Penttilä
2024-08-26 2:56 ` zhiguojiang
2024-08-26 4:30 ` Mika Penttilä
2024-08-25 6:42 ` Lorenzo Stoakes
2024-08-25 7:08 ` zhiguojiang
2024-08-26 17:03 ` David Hildenbrand
-- strict thread matches above, loose matches on Subject: below --
2024-08-23 14:01 Zhiguo Jiang
2024-08-26 17:24 ` David Hildenbrand
2024-08-27 1:50 ` zhiguojiang
2024-08-27 17:35 ` David Hildenbrand
2024-08-28 1:14 ` zhiguojiang
2024-08-28 3:51 ` Mika Penttilä
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=20240823223559.942b53cea16d5cfc6b70bf2d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=justinjiang@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=opensource.kernel@vivo.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