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 19:34:04 +0300 [thread overview]
Message-ID: <20160321163404.GA141069@black.fi.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1603211121210.26353@east.gentwo.org>
On Mon, Mar 21, 2016 at 11:25:09AM -0500, Christoph Lameter wrote:
> On Mon, 21 Mar 2016, Kirill A. Shutemov wrote:
>
> > PAGE_CACHE_{SIZE,SHIFT,MASK,ALIGN} macros were introduced *long* time ago
> > with promise that one day it will be possible to implement page cache with
> > bigger chunks than PAGE_SIZE.
> >
> > This promise never materialized. And unlikely will.
>
> So we decided that we are never going to put THP pages on a LRU?
Err?.. What?
We do have anon-THP pages on LRU. My huge tmpfs patchset also put
file-THPs on LRU list.
The patchset has nothing to do with THP or them being on LRU.
> 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.
Anyway, it's out of scope of the patchset.
--
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>
WARNING: multiple messages have this Message-ID (diff)
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 19:34:04 +0300 [thread overview]
Message-ID: <20160321163404.GA141069@black.fi.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1603211121210.26353@east.gentwo.org>
On Mon, Mar 21, 2016 at 11:25:09AM -0500, Christoph Lameter wrote:
> On Mon, 21 Mar 2016, Kirill A. Shutemov wrote:
>
> > PAGE_CACHE_{SIZE,SHIFT,MASK,ALIGN} macros were introduced *long* time ago
> > with promise that one day it will be possible to implement page cache with
> > bigger chunks than PAGE_SIZE.
> >
> > This promise never materialized. And unlikely will.
>
> So we decided that we are never going to put THP pages on a LRU?
Err?.. What?
We do have anon-THP pages on LRU. My huge tmpfs patchset also put
file-THPs on LRU list.
The patchset has nothing to do with THP or them being on LRU.
> 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.
Anyway, it's out of scope of the patchset.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2016-03-21 16:34 UTC|newest]
Thread overview: 31+ 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 ` 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 12:45 ` Michal Hocko
2016-03-21 17:02 ` Linus Torvalds
2016-03-21 17:02 ` Linus Torvalds
2016-03-21 17:07 ` Kirill A. Shutemov
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:06 ` Kirill A. Shutemov
2016-03-21 12:51 ` Michal Hocko
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:06 ` Kirill A. Shutemov
2016-03-21 12:53 ` Michal Hocko
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:25 ` Christoph Lameter
2016-03-21 16:34 ` Kirill A. Shutemov [this message]
2016-03-21 16:34 ` Kirill A. Shutemov
2016-03-21 16:59 ` Christoph Lameter
2016-03-21 16:59 ` Christoph Lameter
2016-03-21 17:06 ` Kirill A. Shutemov
2016-03-21 17:06 ` Kirill A. Shutemov
2016-03-21 17:29 ` Christoph Lameter
2016-03-21 17:29 ` Christoph Lameter
2016-03-22 10:41 ` Kirill A. Shutemov
2016-03-22 10:41 ` Kirill A. Shutemov
2016-03-22 15:20 ` Christoph Lameter
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=20160321163404.GA141069@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 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.