From: Michal Hocko <mhocko@kernel.org>
To: William Kucharski <william.kucharski@oracle.com>
Cc: lsf-pc@lists.linux-foundation.org, Linux-MM <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM TOPIC ][LSF/MM ATTEND] Read-only Mapping of Program Text using Large THP Pages
Date: Wed, 20 Feb 2019 14:27:34 +0100 [thread overview]
Message-ID: <20190220132734.GC4525@dhcp22.suse.cz> (raw)
In-Reply-To: <E419EE42-B9DC-4612-8B40-5AEBB9CCDD93@oracle.com>
On Wed 20-02-19 06:18:47, William Kucharski wrote:
>
>
> > On Feb 20, 2019, at 5:10 AM, Michal Hocko <mhocko@kernel.org> wrote:
> >
> > On Wed 20-02-19 04:17:13, William Kucharski wrote:
> >> For the past year or so I have been working on further developing my original
> >> prototype support of mapping read-only program text using large THP pages.
> >
> > Song Liu has already proposed THP on FS topic already [1]
> >
> > [1] http://lkml.kernel.org/r/77A00946-D70D-469D-963D-4C4EA20AE4FA@fb.com
> > and I assume this is essentially leading to the same discussion, right?
> > So we can merge this requests.
>
> Different approaches but the same basic issue, yes.
OK, I will mark it as a separate topic then.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-02-20 13:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 11:17 [LSF/MM TOPIC ][LSF/MM ATTEND] Read-only Mapping of Program Text using Large THP Pages William Kucharski
2019-02-20 12:10 ` Michal Hocko
2019-02-20 13:18 ` William Kucharski
2019-02-20 13:27 ` Michal Hocko [this message]
2019-02-20 13:44 ` Matthew Wilcox
2019-02-20 14:07 ` William Kucharski
2019-02-20 14:43 ` Matthew Wilcox
2019-02-20 16:39 ` Keith Busch
2019-02-20 17:19 ` Matthew Wilcox
2019-04-08 11:36 ` William Kucharski
2019-04-28 20:08 ` Song Liu
2019-04-30 12:12 ` 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=20190220132734.GC4525@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--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).