From: Hillf Danton <hdanton@sina.com>
To: Song Liu <songliubraving@fb.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"matthew.wilcox@oracle.com" <matthew.wilcox@oracle.com>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"kernel-team@fb.com" <kernel-team@fb.com>,
"william.kucharski@oracle.com" <william.kucharski@oracle.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"hdanton@sina.com" <hdanton@sina.com>
Subject: Re: [PATCH v7 5/6] mm,thp: add read-only THP support for (non-shmem) FS
Date: Mon, 24 Jun 2019 11:16:04 +0800 [thread overview]
Message-ID: <20190624031604.7764-1-hdanton@sina.com> (raw)
Hello
On Sun, 23 Jun 2019 13:48:47 +0800 Song Liu wrote:
> This patch is (hopefully) the first step to enable THP for non-shmem
> filesystems.
>
> This patch enables an application to put part of its text sections to THP
> via madvise, for example:
>
> madvise((void *)0x600000, 0x200000, MADV_HUGEPAGE);
>
> We tried to reuse the logic for THP on tmpfs.
>
> Currently, write is not supported for non-shmem THP. khugepaged will only
> process vma with VM_DENYWRITE. The next patch will handle writes, which
> would only happen when the vma with VM_DENYWRITE is unmapped.
>
> An EXPERIMENTAL config, READ_ONLY_THP_FOR_FS, is added to gate this
> feature.
>
> Acked-by: Rik van Riel <riel@surriel.com>
> Signed-off-by: Song Liu <songliubraving@fb.com>
> ---
> mm/Kconfig | 11 ++++++
> mm/filemap.c | 4 +--
> mm/khugepaged.c | 90 ++++++++++++++++++++++++++++++++++++++++---------
> mm/rmap.c | 12 ++++---
> 4 files changed, 96 insertions(+), 21 deletions(-)
>
> diff --git a/mm/Kconfig b/mm/Kconfig
> index f0c76ba47695..0a8fd589406d 100644
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -762,6 +762,17 @@ config GUP_BENCHMARK
>
> See tools/testing/selftests/vm/gup_benchmark.c
>
> +config READ_ONLY_THP_FOR_FS
> + bool "Read-only THP for filesystems (EXPERIMENTAL)"
> + depends on TRANSPARENT_HUGE_PAGECACHE && SHMEM
> +
The ext4 mentioned in the cover letter, along with the subject line of
this patch, suggests the scissoring of SHMEM.
> + help
> + Allow khugepaged to put read-only file-backed pages in THP.
> +
> + This is marked experimental because it is a new feature. Write
> + support of file THPs will be developed in the next few release
> + cycles.
> +
> config ARCH_HAS_PTE_SPECIAL
> bool
Hillf
next reply other threads:[~2019-06-24 3:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 3:16 Hillf Danton [this message]
2019-06-24 4:27 ` [PATCH v7 5/6] mm,thp: add read-only THP support for (non-shmem) FS Song Liu
-- strict thread matches above, loose matches on Subject: below --
2019-06-24 7:48 [PATCH v7 5/6] mm,thp: add read-only THP support for (non-shmem)FS Hillf Danton
2019-06-24 21:17 ` Song Liu
2019-06-23 5:47 [PATCH v7 0/6] Enable THP for text section of non-shmem files Song Liu
2019-06-23 5:47 ` [PATCH v7 5/6] mm,thp: add read-only THP support for (non-shmem) FS Song Liu
2019-06-24 12:47 ` Kirill A. Shutemov
2019-06-24 14:01 ` Song Liu
2019-06-24 14:27 ` Kirill A. Shutemov
2019-06-24 14:42 ` Song Liu
2019-06-24 14:54 ` Kirill A. Shutemov
2019-06-24 15:04 ` Song Liu
2019-06-24 15:15 ` Kirill A. Shutemov
2019-06-24 16:33 ` 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=20190624031604.7764-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=akpm@linux-foundation.org \
--cc=kernel-team@fb.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.wilcox@oracle.com \
--cc=songliubraving@fb.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