From: zhiguojiang <justinjiang@vivo.com>
To: David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: opensource.kernel@vivo.com
Subject: Re: [PATCH] mm/rmap: vm_flags including VM_EXEC can exit timely
Date: Wed, 25 Oct 2023 11:04:46 +0800 [thread overview]
Message-ID: <d2d78a5b-fa57-4e46-950d-e8e48bb020be@vivo.com> (raw)
In-Reply-To: <d1c01214-4548-414d-be84-21c38cfe3ede@vivo.com>
在 2023/10/25 9:17, zhiguojiang 写道:
>
>
> 在 2023/10/24 23:51, David Hildenbrand 写道:
>> On 24.10.23 16:49, Zhiguo Jiang wrote:
>>> When pra->vm_flags include VM_EXEC flag and folio is file detected in
>>> folio_referenced_one(), the folio referenced traversal process can be
>>> exited timely to reduce the detecting folio referenced time.
>>>
>>
>> Can you further elaborate what the logic behind that is?
>>
>> Why can we stop here if we're dealing with a pagecache folio in an
>> executable VMA?
>>
> Functions call flow:folio_referenced() --> rmap_walk() -->
> rmap_walk_ksm()/rmap_walk_anon()/rmap_walk_file() --> rwc->rmap_one()
> --> folio_referenced_one(). And folio_referenced() is called by two
> interfaces: folio_check_references() and shrink_active_list().
>
> 1. folio_check_references():
> When (referenced_ptes > 0 && (vm_flags & VM_EXEC) &&
> folio_is_file_lru(folio)) is detected in folio_check_references(),
> FOLIOREF_ACTIVATE will be returned and the folio will be added to the
> active file lru. So when VM_EXEC is detected in
> folio_referenced_one(), we can stop continuing to detect the reference
> relationship between this folio and other vmas, and exit directly to
> avoid unnecessary traversal.
>
> 2. shrink_active_list():
> The shrink_active_list() is the same as the folio_check_references().
>
>>> Signed-off-by: Zhiguo Jiang <justinjiang@vivo.com>
>>> ---
>>> mm/rmap.c | 2 ++
>>> 1 file changed, 2 insertions(+)
>>> mode change 100644 => 100755 mm/rmap.c
>>>
>>> diff --git a/mm/rmap.c b/mm/rmap.c
>>> index 7a27a2b41802..932f3b7e8521
>>> --- a/mm/rmap.c
>>> +++ b/mm/rmap.c
>>> @@ -884,6 +884,8 @@ static bool folio_referenced_one(struct folio
>>> *folio,
>>> if (referenced) {
>>> pra->referenced++;
>>> pra->vm_flags |= vma->vm_flags & ~VM_LOCKED;
>>> + if ((pra->vm_flags | VM_EXEC) && folio_is_file_lru(folio))
>>> + return false;
>>> }
>>> if (!pra->mapcount)
Sorry, Patch mistake in writing, patch should be:
+ if ((pra->vm_flags & VM_EXEC) && folio_is_file_lru(folio))
+ return false;
>>
>
next prev parent reply other threads:[~2023-10-25 3:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 14:49 [PATCH] mm/rmap: vm_flags including VM_EXEC can exit timely Zhiguo Jiang
2023-10-24 15:51 ` David Hildenbrand
2023-10-25 1:17 ` zhiguojiang
2023-10-25 3:04 ` zhiguojiang [this message]
2023-10-25 15:04 ` David Hildenbrand
2023-10-26 2:04 ` zhiguojiang
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=d2d78a5b-fa57-4e46-950d-e8e48bb020be@vivo.com \
--to=justinjiang@vivo.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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