From: Wei Yang <richard.weiyang@gmail.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
akpm@linux-foundation.org, Liam.Howlett@oracle.com,
vbabka@suse.cz, jannh@google.com, linux-mm@kvack.org
Subject: Re: [PATCH] mm/vma: check retry_merge only for new vma case
Date: Mon, 18 Nov 2024 12:34:39 +0000 [thread overview]
Message-ID: <20241118123439.4zi7ebdelwg6e6wh@master> (raw)
In-Reply-To: <a8c1b4fb-af27-4300-b6f7-2cab8fbac2af@lucifer.local>
On Mon, Nov 18, 2024 at 10:04:44AM +0000, Lorenzo Stoakes wrote:
>On Mon, Nov 18, 2024 at 02:18:23AM +0000, Wei Yang wrote:
>> 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>
>
>Nack.
>
>As I said to you in another patch, the aim isn't to find the mathematically
>smallest size of patch. The aim is to keep things readable and nesting
>things like this works against that aim.
>
IMHO, by nesting it, readers will notice this case only happens for new vma
case. So we don't need to retry if vma_merge_new_range() succeed.
It seems to be more readable, but maybe you have other thoughts I missed. If
you would like to share some thoughts, I'd appreciate.
>Unless you can demonstrate a _significant_ perf improvement for not
>checking a boolean here, then you're making the code more complicated than
>it needs to be for no gain.
>
>Right now it's (intentionally!) simple - try to merge, ok we can't, try to
>map a new VMA. Finally, if the state says retry a merge, do it.
>
So you want to make retry_merge a universal check state?
>It's easy to read and easy to understand.
>
>Nesting as you say takes away from that.
>
>I also could have gone through this mmap() code and tried to reach some
>mathematically perfect level of avoiding unnecessary things, but as this
>wasn't the aim, I didn't.
>
>Please try to focus on finding bugs, or _demonstrable_ perf issues rather
>than stuff like this.
>
>Thanks!
>
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2024-11-18 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 2:18 Wei Yang
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 [this message]
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=20241118123439.4zi7ebdelwg6e6wh@master \
--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