From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Dave Hansen <dave.hansen@intel.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [PATCH] thp, mlock: update unevictable-lru.txt
Date: Tue, 15 Mar 2016 18:42:58 +0300 [thread overview]
Message-ID: <20160315154258.GB16462@node.shutemov.name> (raw)
In-Reply-To: <56E82AAE.8090003@intel.com>
On Tue, Mar 15, 2016 at 08:30:54AM -0700, Dave Hansen wrote:
> On 03/15/2016 07:55 AM, Kirill A. Shutemov wrote:
> > +Transparent huge page is represented by single entry on a lru list and
> > +therefore we can only make unevictable entire compound page, not
> > +individual subpages.
>
> A few grammar nits:
>
> A transparent huge page is represented by a single entry on an lru list.
> Therefore, we can only make unevictable an entire compound page, not
> individual subpages.
Thanks.
> > +We handle this by forbidding mlocking PTE-mapped huge pages. This way we
> > +keep the huge page accessible for vmscan. Under memory pressure the page
> > +will be split, subpages from VM_LOCKED VMAs moved to unevictable lru and
> > +the rest can be evicted.
>
> What do you mean by "mlocking" in this context? Do you mean that we
> actually return -ESOMETHING from mlock() on PTE-mapped huge pages? Or,
> do you just mean that we defer treating PTE-mapped huge pages as
> PageUnevictable() inside the kernel?
The latter.
> I think we should probably avoid saying "mlocking" when we really mean
> "kernel-internal mlocked page handling" aka. the unevictable list.
What about
"We handle this by keeping PTE-mapped huge pages on normal LRU lists."
?
The updated patch is below.
next prev parent reply other threads:[~2016-03-15 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 14:55 [PATCH] thp, mlock: update unevictable-lru.txt Kirill A. Shutemov
2016-03-15 15:30 ` Dave Hansen
2016-03-15 15:42 ` Kirill A. Shutemov [this message]
2016-03-15 16:56 ` Kirill A. Shutemov
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=20160315154258.GB16462@node.shutemov.name \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.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).