From: "Jakub Matěna" <matenajakub@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, Vlastimil Babka <vbabka@suse.cz>,
mhocko@kernel.org, mgorman@techsingularity.net,
willy@infradead.org, Liam Howlett <liam.howlett@oracle.com>,
Hugh Dickins <hughd@google.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
riel@surriel.com, rostedt@goodmis.org, peterz@infradead.org
Subject: Re: [PATCH v2 2/2] [PATCH 2/2] mm: add merging after mremap resize
Date: Mon, 30 May 2022 13:15:03 +0200 [thread overview]
Message-ID: <CABsDyaK87nC_bJ1OAc9LOsL53M7qrfkkoO-QzSwGhtt=Np0p2w@mail.gmail.com> (raw)
In-Reply-To: <20220529164718.ed1eac7d614804c825fae9fd@linux-foundation.org>
On Mon, May 30, 2022 at 1:47 AM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Fri, 27 May 2022 23:17:08 +0200 Jakub Matěna <matenajakub@gmail.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
prev parent reply other threads:[~2022-05-30 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 21:17 [PATCH v2 0/2] Refactor of vma_merge and new merge call Jakub Matěna
2022-05-27 21:17 ` [PATCH v2 1/2] [PATCH 1/2] mm: refactor of vma_merge() Jakub Matěna
2022-05-27 21:17 ` [PATCH v2 2/2] [PATCH 2/2] mm: add merging after mremap resize Jakub Matěna
2022-05-29 23:47 ` Andrew Morton
2022-05-30 11:15 ` Jakub Matěna [this message]
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='CABsDyaK87nC_bJ1OAc9LOsL53M7qrfkkoO-QzSwGhtt=Np0p2w@mail.gmail.com' \
--to=matenajakub@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=patches@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=rostedt@goodmis.org \
--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