From: William Kucharski <william.kucharski@oracle.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
"Kirill A. Shutemov" <kirill@shutemov.name>,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] mm, THP: Map read-only text segments using large THP pages
Date: Thu, 17 May 2018 08:34:56 -0600 [thread overview]
Message-ID: <59D5F452-4710-4CE9-9072-E587551D4862@oracle.com> (raw)
In-Reply-To: <20180517075740.GA31969@dhcp22.suse.cz>
> On May 17, 2018, at 1:57 AM, Michal Hocko <mhocko@kernel.org> wrote:
>
> [CCing Kirill and fs-devel]
>
> On Mon 14-05-18 07:12:13, William Kucharski wrote:
>> One of the downsides of THP as currently implemented is that it only supports
>> large page mappings for anonymous pages.
>
> There is a support for shmem merged already. ext4 was next on the plan
> AFAIR but I haven't seen any patches and Kirill was busy with other
> stuff IIRC.
I couldn't find anything that would specifically map text pages with large pages,
so perhaps this could be integrated with that or I may have simply missed changes
that would ultimately provide that functionality.
>
>> I embarked upon this prototype on the theory that it would be advantageous to
>> be able to map large ranges of read-only text pages using THP as well.
>
> Can the fs really support THP only for read mappings? What if those
> pages are to be shared in a writable mapping as well? In other words
> can this all work without a full THP support for a particular fs?
The integration with the page cache would indeed require filesystem support.
The end result I'd like to see is full R/W support for large THP pages; I
thought the RO text mapping proof of concept worthwhile to see what kind of
results we might see and what the thoughts of the community were.
Thanks for the feedback.
-- Bill
next prev parent reply other threads:[~2018-05-17 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 13:12 [RFC] mm, THP: Map read-only text segments using large THP pages William Kucharski
2018-05-14 15:19 ` Christopher Lameter
2018-05-15 6:59 ` William Kucharski
2018-05-17 7:57 ` Michal Hocko
2018-05-17 14:34 ` William Kucharski [this message]
2018-05-17 15:23 ` Matthew Wilcox
2018-05-17 15:40 ` Larry Bassel
2018-05-17 17:31 ` William Kucharski
2018-05-20 6:26 ` 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=59D5F452-4710-4CE9-9072-E587551D4862@oracle.com \
--to=william.kucharski@oracle.com \
--cc=kirill@shutemov.name \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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).