From: Song Liu <songliubraving@fb.com>
To: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<akpm@linux-foundation.org>
Cc: <matthew.wilcox@oracle.com>, <kirill.shutemov@linux.intel.com>,
<oleg@redhat.com>, <kernel-team@fb.com>,
<william.kucharski@oracle.com>, <srikar@linux.vnet.ibm.com>,
Song Liu <songliubraving@fb.com>
Subject: [PATCH 0/2] khugepaged: collapse pmd for pte-mapped THP
Date: Sun, 28 Jul 2019 22:43:33 -0700 [thread overview]
Message-ID: <20190729054335.3241150-1-songliubraving@fb.com> (raw)
This set is the newer version of 5/6 and 6/6 of [1]. v9 of 1-4 of
the work [2] was recently picked by Andrew.
Patch 1 enables khugepaged to handle pte-mapped THP. These THPs are left
in such state when khugepaged failed to get exclusive lock of mmap_sem.
Patch 2 leverages work in 1 for uprobe on THP. After [2], uprobe only
splits the PMD. When the uprobe is disabled, we get pte-mapped THP.
After this set, these pte-mapped THP will be collapsed as pmd-mapped.
[1] https://lkml.org/lkml/2019/6/23/23
[2] https://www.spinics.net/lists/linux-mm/msg185889.html
Song Liu (2):
khugepaged: enable collapse pmd for pte-mapped THP
uprobe: collapse THP pmd after removing all uprobes
include/linux/khugepaged.h | 15 ++++
kernel/events/uprobes.c | 9 +++
mm/khugepaged.c | 136 +++++++++++++++++++++++++++++++++++++
3 files changed, 160 insertions(+)
--
2.17.1
next reply other threads:[~2019-07-29 5:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 5:43 Song Liu [this message]
2019-07-29 5:43 ` [PATCH 1/2] khugepaged: enable collapse pmd for pte-mapped THP Song Liu
2019-07-30 14:59 ` Kirill A. Shutemov
2019-07-30 17:28 ` Song Liu
2019-07-30 18:39 ` Song Liu
2019-07-29 5:43 ` [PATCH 2/2] uprobe: collapse THP pmd after removing all uprobes Song Liu
2019-07-30 15:01 ` Kirill A. Shutemov
2019-07-30 17:02 ` Song Liu
2019-07-31 16:16 ` Oleg Nesterov
2019-07-31 16:36 ` Song Liu
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=20190729054335.3241150-1-songliubraving@fb.com \
--to=songliubraving@fb.com \
--cc=akpm@linux-foundation.org \
--cc=kernel-team@fb.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.wilcox@oracle.com \
--cc=oleg@redhat.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=william.kucharski@oracle.com \
/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).