From: David Hildenbrand <david@redhat.com>
To: Zhiguo Jiang <justinjiang@vivo.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
oe-lkp@lists.linux.dev, oliver.sang@intel.com
Cc: opensource.kernel@vivo.com
Subject: Re: [PATCH v2] vma remove the unneeded avc bound with non-CoWed folio
Date: Mon, 26 Aug 2024 19:24:45 +0200 [thread overview]
Message-ID: <2f19c2ff-66b2-4860-a870-a1bffe73320c@redhat.com> (raw)
In-Reply-To: <20240823140139.263-1-justinjiang@vivo.com>
On 23.08.24 16:01, Zhiguo Jiang 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.
>
> Signed-off-by: Zhiguo Jiang <justinjiang@vivo.com>
> ---
> -v2:
> * Solve the kernel test robot noticed "WARNING"
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Closes: https://lore.kernel.org/oe-lkp/202408230938.43f55b4-lkp@intel.com
> * Update comments to more accurately describe this patch.
>
> -v1:
> https://lore.kernel.org/linux-mm/20240820143359.199-1-justinjiang@vivo.com/
>
> include/linux/rmap.h | 1 +
> mm/memory.c | 8 +++++++
> mm/rmap.c | 53 ++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 62 insertions(+)
>
> diff --git a/include/linux/rmap.h b/include/linux/rmap.h
> index 91b5935e8485..8607d28a3146
> --- a/include/linux/rmap.h
> +++ b/include/linux/rmap.h
> @@ -257,6 +257,7 @@ void folio_remove_rmap_ptes(struct folio *, struct page *, int nr_pages,
> folio_remove_rmap_ptes(folio, page, 1, vma)
> void folio_remove_rmap_pmd(struct folio *, struct page *,
> struct vm_area_struct *);
> +void folio_remove_anon_avc(struct folio *, struct vm_area_struct *);
>
> void hugetlb_add_anon_rmap(struct folio *, struct vm_area_struct *,
> unsigned long address, rmap_t flags);
> diff --git a/mm/memory.c b/mm/memory.c
> index 93c0c25433d0..4c89cb1cb73e
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -3428,6 +3428,14 @@ static vm_fault_t wp_page_copy(struct vm_fault *vmf)
> * old page will be flushed before it can be reused.
> */
> folio_remove_rmap_pte(old_folio, vmf->page, vma);
> +
> + /*
> + * If the new_folio's anon_vma is different from the
> + * old_folio's anon_vma, the avc binding relationship
> + * between vma and the old_folio's anon_vma is removed,
> + * avoiding rmap redundant overhead.
> + */
> + folio_remove_anon_avc(old_folio, vma);
... by increasing write fault latency, introducing an RMAP walk (!)? Hmm?
On the reuse path, we do a folio_move_anon_rmap(), to optimize that.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-08-26 17:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 14:01 [PATCH v2] vma remove the unneeded avc bound with non-CoWed folio Zhiguo Jiang
2024-08-26 17:24 ` David Hildenbrand [this message]
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ä
-- strict thread matches above, loose matches on Subject: below --
2024-08-23 15:02 Zhiguo Jiang
2024-08-24 5:35 ` Andrew Morton
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
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=2f19c2ff-66b2-4860-a870-a1bffe73320c@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=justinjiang@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).