linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@fb.com>
To: "lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-raid <linux-raid@vger.kernel.org>,
	"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>
Subject: [LSF/MM TOPIC] (again) THP for file systems
Date: Wed, 13 Feb 2019 22:00:10 +0000	[thread overview]
Message-ID: <77A00946-D70D-469D-963D-4C4EA20AE4FA@fb.com> (raw)

Hi,

I would like to attend the LSF/MM Summit 2019. I'm interested in topics about
BPF, mdraid, and MM. I am a designated reviewer of BPF. I am also helping Jens
organize mdraid patches.

I would like to discuss remaining work to bring THP to (non-tmpfs) file systems.
This topic has been discussed multiple times in previous LSF/MM summits [1][2].
However, there hasn't been much progress since late 2017 (the latest work I can
find is by Kirill A. Shutemov [3]).

We (Facebook) uses THP in many services. We see significant savings by putting
hot-text on THP. To achieve this with state-of-the-art Linux Kernel, we have to
either: trick the Kernel to believe certain region is anonymous pages; or put
the executable in tmpfs. In our case, the tmpfs solution is too expensive.
Therefore, we use a hack to trick the Kernel. This hack breaks other useful
features, e.g. perf symbols and uprobes. Instead of introducing more hacks to
use these broken features, it is better to enable THP for file systems.
Therefore, we would like discuss (for one more time) what is needed to bring
THP to file systems like ext4, xfs, btrfs, etc. Once we are aligned on the
direction, we are more than happy to commit time and resource to make it happen.

Since this topic is my main focus of this year's summit, I would like an invite
to the MM track.

Thanks,
Song

[1] https://lwn.net/Articles/686690/
[2] https://lwn.net/Articles/718102/
[3] https://kernel.googlesource.com/pub/scm/linux/kernel/git/kas/linux/+/hugeext4/wip

             reply	other threads:[~2019-02-13 22:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 22:00 Song Liu [this message]
2019-02-13 23:59 ` Matthew Wilcox
2019-02-14  1:59   ` Song Liu
2019-02-14 17:10     ` Wols Lists
2019-02-14 10:55   ` William Kucharski

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=77A00946-D70D-469D-963D-4C4EA20AE4FA@fb.com \
    --to=songliubraving@fb.com \
    --cc=bpf@vger.kernel.org \
    --cc=kirill@shutemov.name \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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