From: Wei Yang <richard.weiyang@gmail.com>
To: akpm@linux-foundation.org, Liam.Howlett@oracle.com,
lorenzo.stoakes@oracle.com, vbabka@suse.cz, jannh@google.com
Cc: linux-mm@kvack.org, Wei Yang <richard.weiyang@gmail.com>,
"Liam R . Howlett" <Liam.Howlett@Oracle.com>
Subject: [PATCH] mm/vma: check retry_merge only for new vma case
Date: Mon, 18 Nov 2024 02:18:23 +0000 [thread overview]
Message-ID: <20241118021823.17386-1-richard.weiyang@gmail.com> (raw)
Current code logic looks like this:
__mmap_region()
vma = vma_merge_new_range(&vmg)
if (!vma)
__mmap_new_vma(&map, &vma)
__mmap_new_file_vma(map, vma)
map->retry_merge = xxx --- (1)
if (map.retry_merge)
vma_merge_existing_range(vmg, &map, vma)
Location (1) is the only place where map.retry_merge is set, this means
it is not necessary to check it if already merged with adjacent vma.
Let's move the check and following operation into new vma case.
Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
CC: Liam R. Howlett <Liam.Howlett@Oracle.com>
CC: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
CC: Vlastimil Babka <vbabka@suse.cz>
CC: Jann Horn <jannh@google.com>
---
mm/vma.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/mm/vma.c b/mm/vma.c
index 8a454a7bbc80..80b1bd404f23 100644
--- a/mm/vma.c
+++ b/mm/vma.c
@@ -2456,14 +2456,14 @@ unsigned long __mmap_region(struct file *file, unsigned long addr,
error = __mmap_new_vma(&map, &vma);
if (error)
goto unacct_error;
- }
- /* If flags changed, we might be able to merge, so try again. */
- if (map.retry_merge) {
- VMG_MMAP_STATE(vmg, &map, vma);
+ /* If flags changed, we might be able to merge, so try again. */
+ if (map.retry_merge) {
+ VMG_MMAP_STATE(vmg, &map, vma);
- vma_iter_config(map.vmi, map.addr, map.end);
- vma_merge_existing_range(&vmg);
+ vma_iter_config(map.vmi, map.addr, map.end);
+ vma_merge_existing_range(&vmg);
+ }
}
__mmap_complete(&map, vma);
--
2.34.1
next reply other threads:[~2024-11-18 2:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 2:18 Wei Yang [this message]
2024-11-18 3:56 ` Liam R. Howlett
2024-11-18 9:31 ` Wei Yang
2024-11-18 10:06 ` Lorenzo Stoakes
2024-11-18 10:04 ` Lorenzo Stoakes
2024-11-18 12:34 ` Wei Yang
2024-11-18 12:52 ` Lorenzo Stoakes
2024-11-19 0:59 ` Wei Yang
2024-11-19 10:14 ` Lorenzo Stoakes
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=20241118021823.17386-1-richard.weiyang@gmail.com \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=vbabka@suse.cz \
/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