[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20220602111341.6674e4d862d6d925b0eebcb3@linux-foundation.org>
Date: Thu, 2 Jun 2022 11:13:41 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Jakub Matěna <matenajakub@...il.com>
Cc: linux-mm@...ck.org, patches@...ts.linux.dev,
linux-kernel@...r.kernel.org, vbabka@...e.cz, mhocko@...nel.org,
mgorman@...hsingularity.net, willy@...radead.org,
liam.howlett@...cle.com, hughd@...gle.com, kirill@...temov.name,
riel@...riel.com, rostedt@...dmis.org, peterz@...radead.org
Subject: Re: [PATCH 1/2] [PATCH 1/2] mm: refactor of vma_merge()
On Thu, 2 Jun 2022 16:56:41 +0200 Jakub Matěna <matenajakub@...il.com> wrote:
> Refactor vma_merge() to make it shorter and more understandable.
> Main change is the elimination of code duplicity in the case of
> merge next check. This is done by first doing checks and caching
> the results before executing the merge itself. The variable 'area' is
> divided into 'mid' and 'res' as previously it was used for two purposes,
> as the middle VMA between prev and next and also as the result of the
> merge itself. Exit paths are also unified.
>
Thanks, but unfortunately the code you're working on here has changed
greatly in Liam's mapletree patchset. Could you please take a look at
the mm-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm and decide if you
want to tackle it?
Powered by blists - more mailing lists