[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241204235632.e44hokoy7izmrdtx@master>
Date: Wed, 4 Dec 2024 23:56:32 +0000
From: Wei Yang <richard.weiyang@...il.com>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@...cle.com>,
Vlastimil Babka <vbabka@...e.cz>, Jann Horn <jannh@...gle.com>,
Eric Biederman <ebiederm@...ssion.com>, Kees Cook <kees@...nel.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] mm/vma: make more mmap logic userland testable
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?
>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?
--
Wei Yang
Help you, Help me
Powered by blists - more mailing lists