From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Christoph Lameter <cl@linux.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
Matthew Wilcox <willy@linux.intel.com>,
Hugh Dickins <hughd@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/3] fs, mm: get rid of PAGE_CACHE_* and page_cache_{get,release} macros
Date: Mon, 21 Mar 2016 20:06:55 +0300 [thread overview]
Message-ID: <20160321170655.GA141158@black.fi.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1603211155280.26653@east.gentwo.org>
On Mon, Mar 21, 2016 at 11:59:25AM -0500, Christoph Lameter wrote:
> On Mon, 21 Mar 2016, Kirill A. Shutemov wrote:
>
> > We do have anon-THP pages on LRU. My huge tmpfs patchset also put
> > file-THPs on LRU list.
>
> So they are on the LRU as 4k units? Tried to look it up.
One entry on LRU per huge page.
> > > Will this actually work if we have really huge memory (100s of TB) where
> > > almost everything is a huge page? Guess we have to use hugetlbfs and we
> > > need to think about this as being exempt from paging.
> >
> > Sorry, I failed to understand your message.
> >
> > Look on huge tmpfs patchset. It allows both small and huge pages in page
> > cache.
>
> Thus my wonder about this patchset. It seems then that the huge pages are
> treated as 4k pages? Otherwise we would have two sizes for pages in the
> page cache. Sorry I did not follow that too closely. Will try finding that
> patchset.
We do have two page sizes in the page cache. It's the only option to get
transparent huge pages transparent.
We have 512 (on x86-64) entries on radix-tree per huge page, but we can
opt to Matthew's multi-order entries later. See e61452365372 "radix_tree:
add support for multi-order entries".
--
Kirill A. Shutemov
--
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>
next prev parent reply other threads:[~2016-03-21 17:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 12:06 [PATCH 0/3] fs, mm: get rid of PAGE_CACHE_* and page_cache_{get,release} macros Kirill A. Shutemov
2016-03-21 12:06 ` [PATCH 1/3] mm, fs: " Kirill A. Shutemov
2016-03-21 12:45 ` Michal Hocko
2016-03-21 17:02 ` Linus Torvalds
2016-03-21 17:07 ` Kirill A. Shutemov
2016-03-21 12:06 ` [PATCH 2/3] mm, fs: remove remaining PAGE_CACHE_* and page_cache_{get,release} usage Kirill A. Shutemov
2016-03-21 12:51 ` Michal Hocko
2016-03-21 12:06 ` [PATCH 3/3] mm: drop PAGE_CACHE_* and page_cache_{get,release} definition Kirill A. Shutemov
2016-03-21 12:53 ` Michal Hocko
2016-03-21 16:25 ` [PATCH 0/3] fs, mm: get rid of PAGE_CACHE_* and page_cache_{get,release} macros Christoph Lameter
2016-03-21 16:34 ` Kirill A. Shutemov
2016-03-21 16:59 ` Christoph Lameter
2016-03-21 17:06 ` Kirill A. Shutemov [this message]
2016-03-21 17:29 ` Christoph Lameter
2016-03-22 10:41 ` Kirill A. Shutemov
2016-03-22 15:20 ` Christoph Lameter
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=20160321170655.GA141158@black.fi.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.intel.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).