From: "Jakub Matěna" <matenajakub@gmail.com>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, vbabka@suse.cz, mhocko@kernel.org,
mgorman@techsingularity.net, willy@infradead.org,
liam.howlett@oracle.com, hughd@google.com, kirill@shutemov.name,
riel@surriel.com, rostedt@goodmis.org, peterz@infradead.org,
"Jakub Matěna" <matenajakub@gmail.com>
Subject: [PATCH v2 0/2] Refactor of vma_merge and new merge call
Date: Fri, 27 May 2022 23:17:06 +0200 [thread overview]
Message-ID: <20220527211708.839033-1-matenajakub@gmail.com> (raw)
I am currently working on my master's thesis trying to increase
number of merges of VMAs currently failing because of page offset
incompatibility and difference in their anon_vmas. The following
refactor and added merge call included in this series is just two
smaller upgrades I created along the way.
The rest of the work is still being worked on but was send to mailing
list as a RFC:
https://lore.kernel.org/all/20220516125405.1675-1-matenajakub@gmail.com/
This patch series is based on tag v5.18-rc2. This is second version,
I forgot to include one header file in the first version.
Jakub Matěna (2):
mm: refactor of vma_merge()
mm: add merging after mremap resize
mm/mmap.c | 87 +++++++++++++++++++++++------------------------------
mm/mremap.c | 8 +++--
2 files changed, 43 insertions(+), 52 deletions(-)
--
2.35.1
next reply other threads:[~2022-05-27 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 21:17 Jakub Matěna [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2022-06-02 14:56 [PATCH v2 0/2] Refactor of vma_merge and new merge call Jakub Matěna
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=20220527211708.839033-1-matenajakub@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;
as well as URLs for NNTP newsgroup(s).