From: Song Liu <songliubraving@fb.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: "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>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [LSF/MM TOPIC] (again) THP for file systems
Date: Thu, 14 Feb 2019 01:59:55 +0000 [thread overview]
Message-ID: <843818E0-C7E8-451E-A5B1-DAF0F120BD5A@fb.com> (raw)
In-Reply-To: <20190213235959.GX12668@bombadil.infradead.org>
> On Feb 13, 2019, at 3:59 PM, Matthew Wilcox <willy@infradead.org> wrote:
>
> On Wed, Feb 13, 2019 at 10:00:10PM +0000, Song Liu wrote:
>> 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]).
>
> ... this was literally just discussed.
>
> Feel free to review
> https://lore.kernel.org/lkml/20190212183454.26062-1-willy@infradead.org/
>
> with particular reference to the last three paragraphs of
> https://lore.kernel.org/lkml/20190208042448.GB21860@bombadil.infradead.org/
Thanks for the pointers! I will read the patches and related code.
>
>> 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.
>
> I believe the direction is clear. It needs people to do the work.
> We're critically short of reviewers. I got precious little review of
> the original XArray work, which made Andrew nervous and delayed its
> integration. Now I'm getting little review of the followup patches
> to lay the groundwork for filesystems to support larger page sizes.
> I have very little patience for this situation.
I don't feel I am a qualified reviewer for MM patches, yet. But I will
try my best to catch up.
Thanks again,
Song
next prev parent reply other threads:[~2019-02-14 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 22:00 [LSF/MM TOPIC] (again) THP for file systems Song Liu
2019-02-13 23:59 ` Matthew Wilcox
2019-02-14 1:59 ` Song Liu [this message]
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=843818E0-C7E8-451E-A5B1-DAF0F120BD5A@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 \
--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).