From: David Hildenbrand <david@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Wei Yang <richard.weiyang@gmail.com>
Cc: 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, 29 Apr 2025 11:38:23 +0200 [thread overview]
Message-ID: <8c268ece-71a7-470a-bf8b-71d3e4920977@redhat.com> (raw)
In-Reply-To: <bc71ef51-d552-4d9f-901c-f40111c7d7cb@lucifer.local>
On 29.04.25 11:31, Lorenzo Stoakes wrote:
> Wei,
>
> NACK the whole series.
>
> I'm really not sure how to get through to you. You were _explicitly_
> advised not to send this series. And yet you've sent it anyway.
>
> I mean, I appreciate your enthusiasm and the fact you've made tests here
> etc. obviously. And you've clearly put a TON of work in. But I just don't
> know why you would when explicitly told not to without at least discussing
> it first?
>
> This just isn't a great way of interacting with the community. We're all
> human, please try to have some empathy for others here, as I really do try
> to have with you as best I can.
>
> This adds a ton of churn and LOCKS IN assumptions about how anon_vma works,
> clashes with other series (most notably series I've been working on), takes
> away from efforts I want to make to start to join file-backed and anon
> reverse mapping logic, separates the two in such a way as to encourage this
> to nonly grow and generally isn't conducive to where I want to go with
> rmap.
anon_vma, the unloved child. :)
I would love to see a simplification that makes it less special, and I
can understand how adding tests for the ways it is special can be
counter-productive.
>
> This is part of why I explicitly told you please don't go down this road,
> because you're likely to end up doing work that doesn't get used. It's not
> a great use of your time either.
>
> Since there's something useful here in tests, I may at a later date come
> back to those.
Agreed, skimming over the tests there are some nice diagrams and cases.
But I would hope that for most of these cases we could test on a higher
level: test our expectations when running real programs that we want to
check, especially when performing internal changes on how we handle anon
memory + rmap.
E.g., do fork(), then test if we can successfully perform rmap
lookups/updates (e.g., migrate folio to a different numa node etc).
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-04-29 9:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 9:06 [RFC Patch 0/5] Make anon_vma operations testable 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 [this message]
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
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=8c268ece-71a7-470a-bf8b-71d3e4920977@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;
as well as URLs for NNTP newsgroup(s).