[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABsDyaK87nC_bJ1OAc9LOsL53M7qrfkkoO-QzSwGhtt=Np0p2w@mail.gmail.com>
Date: Mon, 30 May 2022 13:15:03 +0200
From: Jakub Matěna <matenajakub@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-mm@...ck.org, patches@...ts.linux.dev,
linux-kernel@...r.kernel.org, Vlastimil Babka <vbabka@...e.cz>,
mhocko@...nel.org, mgorman@...hsingularity.net,
willy@...radead.org, Liam Howlett <liam.howlett@...cle.com>,
Hugh Dickins <hughd@...gle.com>,
"Kirill A. Shutemov" <kirill@...temov.name>, riel@...riel.com,
rostedt@...dmis.org, peterz@...radead.org
Subject: Re: [PATCH v2 2/2] [PATCH 2/2] mm: add merging after mremap resize
On Mon, May 30, 2022 at 1:47 AM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Fri, 27 May 2022 23:17:08 +0200 Jakub Matěna <matenajakub@...il.com> wrote:
>
> > When mremap call results in expansion, it might be possible to merge the
> > VMA with the next VMA which might become adjacent. This patch adds
> > vma_merge call after the expansion is done to try and merge.
>
> Thanks.
>
> Would it make sense to add a test case for this in (I assume)
> tools/testing/selftests/vm/mremap_test.c? Maybe parse /proc/self/maps
> and check that the merging occurred as expected?
>
It shouldn't be a problem and it makes sense. I will do it.
Jakub Matěna
Powered by blists - more mailing lists