From: David Hildenbrand <david@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] mm: Rename vm_area_struct to mm_area
Date: Tue, 1 Apr 2025 17:26:00 +0200 [thread overview]
Message-ID: <3c90c3f5-3ec7-4ea9-b482-840f21db52ea@redhat.com> (raw)
In-Reply-To: <47aa41fe-9129-4e12-aa51-987748cff740@lucifer.local>
On 01.04.25 17:20, Lorenzo Stoakes wrote:
> On Tue, Apr 01, 2025 at 05:11:58PM +0200, David Hildenbrand wrote:
>> On 01.04.25 14:25, Matthew Wilcox (Oracle) wrote:
>>> We don't need to put "_struct" on the end of the name. It's obviously
>>> a struct. Just look at the word "struct" before the name. The acronym
>>> "vm" tends to mean "virtual machine" rather than "virtual memory" these
>>> days, so use "mm_area" instead of "vm_area". I decided not to rename
>>> the variables (typically "vma") of type "struct mm_area *" as that would
>>> be a fair bit more disruptive.
>>
>> I almost fell for it, until I looked at the calendar :)
>>
>> On a serious note: "struct vma" ;)
>
> We should put this in a helper struct
>
> Maybe:
>
> struct vmb {
> struct vma *vma;
> bool is_file;
> };
>
> I think this would solve a lot of our problems and probably eliminate
> anon_vma or something
If that solves most our problems, imagine what a "struct vmc" could do :)
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-04-01 15:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 12:25 Matthew Wilcox (Oracle)
2025-04-01 12:35 ` Lorenzo Stoakes
2025-04-01 14:17 ` Liam R. Howlett
2025-04-01 14:21 ` Vlastimil Babka
2025-04-01 14:46 ` Johannes Weiner
2025-04-01 14:54 ` Harry Yoo
2025-04-01 15:17 ` Mike Rapoport
2025-04-01 15:11 ` David Hildenbrand
2025-04-01 15:20 ` Lorenzo Stoakes
2025-04-01 15:26 ` David Hildenbrand [this message]
2025-04-01 23:53 ` John Hubbard
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=3c90c3f5-3ec7-4ea9-b482-840f21db52ea@redhat.com \
--to=david@redhat.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 \
--cc=willy@infradead.org \
/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