From: David Hildenbrand <david@redhat.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
akpm@linux-foundation.org, riel@surriel.com, vbabka@suse.cz,
harry.yoo@oracle.com, jannh@google.com, baohua@kernel.org,
linux-mm@kvack.org
Subject: Re: [RFC Patch 0/5] Make anon_vma operations testable
Date: Tue, 3 Jun 2025 23:31:21 +0200 [thread overview]
Message-ID: <a8088668-18b3-403c-8631-5352292e6231@redhat.com> (raw)
In-Reply-To: <20250530232358.yjx4yqxicvsbvgjw@master>
On 31.05.25 01:23, Wei Yang wrote:
> On Fri, May 30, 2025 at 04:39:21PM +0200, David Hildenbrand wrote:
> [...]
>>>
>>> Here you mean for all anon/shmem/pagecache pages, we could have two category
>>> tests:
>>>
>>> * migrate and write different data from on process, verify each process see
>>> new data
>>> * trigger pageout from one process, verify each process has it pageout
>>> (/proc/self/pagemap)
>>>
>>> While one of these category is enough, right? Just like KSM below, migrate or
>>> pageout.
>>
>> Both cases will trigger different code paths: for example, migration will
>> trigger restoring of migration entries, which is a different rmap operation
>> not triggered by pageout/pagein :)
>>
>> Pageout is probably easier to implement: but we couldn't test hugetlb. With
>> migration we probably could also test hugetlb rmap code (yet another case we
>> should probably cover).
>>
>
> Oh, the pageout/pagein here is the madvise(MADV_PAGEOUT) one you mention in
> your previous reply?
Yes, migration (via move_pages(), but requiring two NUMA nodes) vs.
pageout (via madvise(MADV_PAGEOUT) which would require a similar "force"
way of succeeding on shared pages).
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-06-03 21:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 9:06 Wei Yang
2025-04-29 9:06 ` [RFC Patch 1/5] mm: move anon_vma manipulation functions to own file Wei Yang
2025-04-29 9:06 ` [RFC Patch 2/5] anon_vma: add skeleton code for userland testing of anon_vma logic Wei Yang
2025-05-01 1:31 ` Wei Yang
2025-05-01 9:41 ` Lorenzo Stoakes
2025-05-01 14:45 ` Wei Yang
2025-04-29 9:06 ` [RFC Patch 3/5] anon_vma: add test for mergeable anon_vma Wei Yang
2025-04-29 9:06 ` [RFC Patch 4/5] anon_vma: add test for reusable anon_vma Wei Yang
2025-04-29 9:06 ` [RFC Patch 5/5] anon_vma: add test to assert no double-reuse Wei Yang
2025-04-29 9:31 ` [RFC Patch 0/5] Make anon_vma operations testable Lorenzo Stoakes
2025-04-29 9:38 ` David Hildenbrand
2025-04-29 9:41 ` Lorenzo Stoakes
2025-04-29 23:56 ` Wei Yang
2025-04-30 7:47 ` David Hildenbrand
2025-04-30 15:44 ` Wei Yang
2025-04-30 21:36 ` David Hildenbrand
2025-05-14 1:23 ` Wei Yang
2025-05-27 6:34 ` Wei Yang
2025-05-27 11:31 ` David Hildenbrand
2025-05-28 1:17 ` Wei Yang
2025-05-30 2:11 ` Wei Yang
2025-05-30 8:00 ` David Hildenbrand
2025-05-30 14:05 ` Wei Yang
2025-05-30 14:39 ` David Hildenbrand
2025-05-30 23:23 ` Wei Yang
2025-06-03 21:31 ` David Hildenbrand [this message]
2025-04-29 23:15 ` Wei Yang
2025-04-30 14:38 ` Lorenzo Stoakes
2025-04-30 15:41 ` Wei Yang
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=a8088668-18b3-403c-8631-5352292e6231@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=harry.yoo@oracle.com \
--cc=jannh@google.com \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=richard.weiyang@gmail.com \
--cc=riel@surriel.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