From: Matthew Wilcox <willy@linux.intel.com>
To: Christoph Lameter <cl@linux.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC] Support for 1GB THP
Date: Tue, 1 Mar 2016 16:47:18 -0500 [thread overview]
Message-ID: <20160301214718.GK3730@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1603011025490.31696@east.gentwo.org>
On Tue, Mar 01, 2016 at 10:32:52AM -0600, Christoph Lameter wrote:
> > > - Can we get rid of PAGE_CACHE_SIZE now? Finally? Pretty please?
> >
> > +1 :)
>
> We have had grandiouse visions of being free of that particular set of
> chains for more than 10 years now. Sadly nothing really was that appealing
> and the current state of THP support is not that encouraging as well. We
> rather go with static huge page support to have more control over how
> memory is laid out for a process.
With Kirill's fault-around code in place, I think it delivers all or most
of the benefits promised by increasing PAGE_CACHE_SIZE.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-03-01 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 7:09 [LSF/MM TOPIC] Support for 1GB THP Matthew Wilcox
2016-03-01 10:25 ` [Lsf-pc] " Jan Kara
2016-03-01 11:00 ` Mel Gorman
2016-03-01 11:51 ` Mel Gorman
2016-03-01 12:09 ` Kirill A. Shutemov
2016-03-01 12:52 ` Mel Gorman
2016-03-01 21:44 ` Matthew Wilcox
2016-03-01 22:15 ` Mike Kravetz
2016-03-01 22:33 ` Rik van Riel
2016-03-01 22:36 ` James Bottomley
2016-03-02 14:14 ` Matthew Wilcox
2016-03-01 12:20 ` Kirill A. Shutemov
2016-03-01 16:32 ` Christoph Lameter
2016-03-01 21:47 ` Matthew Wilcox [this message]
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=20160301214718.GK3730@linux.intel.com \
--to=willy@linux.intel.com \
--cc=cl@linux.com \
--cc=kirill@shutemov.name \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.