From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
Eric Biederman <ebiederm@xmission.com>,
Kees Cook <kees@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] mm/vma: make more mmap logic userland testable
Date: Thu, 5 Dec 2024 07:03:08 +0000 [thread overview]
Message-ID: <68dd91e4-b9c3-413c-b284-f43636e7ffba@lucifer.local> (raw)
In-Reply-To: <20241204235632.e44hokoy7izmrdtx@master>
On Wed, Dec 04, 2024 at 11:56:32PM +0000, Wei Yang wrote:
> On Tue, Dec 03, 2024 at 06:05:07PM +0000, Lorenzo Stoakes wrote:
> >This series carries on the work the work started in previous series and
> ^^^ ^^^
>
> Duplicated?
Thanks yes, but trivial enough that I'm not sure it's worth a
correction. Will fix if need to respin.
>
> >continued in commit 52956b0d7fb9 ("mm: isolate mmap internal logic to
> >mm/vma.c"), moving the remainder of memory mapping implementation details
> >logic into mm/vma.c allowing the bulk of the mapping logic to be unit
> >tested.
> >
> >It is highly useful to do so, as this means we can both fundamentally test
> >this core logic, and introduce regression tests to ensure any issues
> >previously resolved do not recur.
> >
> >Vitally, this includes the do_brk_flags() function, meaning we have both
> >core means of userland mapping memory now testable.
> >
> >Performance testing was performed after this change given the brk() system
> >call's sensitivity to change, and no performance regression was observed.
>
> May I ask what performance test is done?
mmtests brk1, brk2 (will-it-scale)
You'd not really expect an impact based on relocation of this code, but
with brk it's always worth checking...
>
>
> --
> Wei Yang
> Help you, Help me
next prev parent reply other threads:[~2024-12-05 7:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 18:05 Lorenzo Stoakes
2024-12-03 18:05 ` [PATCH 1/5] mm/vma: move brk() internals to mm/vma.c Lorenzo Stoakes
2024-12-04 11:55 ` kernel test robot
2024-12-04 12:10 ` Lorenzo Stoakes
2024-12-04 12:08 ` Lorenzo Stoakes
2024-12-04 13:10 ` kernel test robot
2024-12-03 18:05 ` [PATCH 2/5] mm/vma: move unmapped_area() " Lorenzo Stoakes
2024-12-03 18:05 ` [PATCH 3/5] mm: abstract get_arg_page() stack expansion and mmap read lock Lorenzo Stoakes
2024-12-05 0:18 ` Wei Yang
2024-12-05 7:01 ` Lorenzo Stoakes
2024-12-08 11:27 ` Wei Yang
2024-12-09 10:47 ` Lorenzo Stoakes
2024-12-05 7:06 ` Lorenzo Stoakes
2024-12-10 17:14 ` Jann Horn
2024-12-14 1:05 ` Kees Cook
2024-12-03 18:05 ` [PATCH 4/5] mm/vma: move stack expansion logic to mm/vma.c Lorenzo Stoakes
2024-12-03 18:05 ` [PATCH 5/5] mm/vma: move __vm_munmap() " Lorenzo Stoakes
2024-12-04 23:56 ` [PATCH 0/5] mm/vma: make more mmap logic userland testable Wei Yang
2024-12-05 7:03 ` Lorenzo Stoakes [this message]
2024-12-06 0:30 ` Wei Yang
2024-12-09 10:35 ` 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=68dd91e4-b9c3-413c-b284-f43636e7ffba@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@gmail.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
/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