From: Hugh Dickins <hughd@google.com>
To: Hugh Dickins <hughd@google.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: avoid tail page refcounting on non-THP compound pages
Date: Wed, 25 Mar 2015 15:48:48 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.11.1503251545510.4490@eggly.anvils> (raw)
In-Reply-To: <alpine.LSU.2.11.1503251544120.4490@eggly.anvils>
On Wed, 25 Mar 2015, Hugh Dickins wrote:
> On Thu, 26 Mar 2015, Kirill A. Shutemov wrote:
>
> > THP uses tail page refcounting to be able to split huge page at any
> > time. Tail page refcounting is not needed for rest users of compound
> > pages and it's harmful because of overhead.
> >
> > We try to exclude non-THP pages from tail page refcounting using
> > __compound_tail_refcounted() check. It excludes most common non-THP
> > compound pages: SL*B and hugetlb, but it doesn't catch rest of
> > __GFP_COMP users -- drivers.
> >
> > And it's not only about overhead.
> >
> > Drivers might want to use compound pages to get refcounting semantics
> > suitable for mapping high-order pages to userspace. But tail page
> > refcounting breaks it.
> >
> > Tail page refcounting uses ->_mapcount in tail pages to store GUP pins
> > on them. It means GUP pins would affect page_mapcount() for tail pages.
> > It's not a problem for THP, because it never maps tail pages. But unlike
> > THP, drivers map parts of compound pages with PTEs and it makes
> > page_mapcount() be called for tail pages.
> >
> > In particular, GUP pins would shift PSS up and affect /proc/kpagecount
> > for such pages. But, I'm not aware about anything which can lead to
> > crash or other serious misbehaviour.
> >
> > Since currently all THP pages are anonymous and all drivers pages are
> > not, we can fix the __compound_tail_refcounted() check by requiring
> > PageAnon() to enable tail page refcounting.
> >
> > Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
>
> Acked-by: Hugh Dickins <hughd@google.com>
Oh, hold on a moment: does this actually build in a tree without your
page-flags.h consolidation? It didn't when I tried to add a PageAnon
test there for my series against v3.19, has something changed in v4.0?
>
> > ---
> > include/linux/mm.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/linux/mm.h b/include/linux/mm.h
> > index 4a3a38522ab4..16fe322b66ea 100644
> > --- a/include/linux/mm.h
> > +++ b/include/linux/mm.h
> > @@ -456,7 +456,7 @@ static inline int page_count(struct page *page)
> >
> > static inline bool __compound_tail_refcounted(struct page *page)
> > {
> > - return !PageSlab(page) && !PageHeadHuge(page);
> > + return PageAnon(page) && !PageSlab(page) && !PageHeadHuge(page);
> > }
> >
> > /*
> > --
> > 2.1.4
--
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:[~2015-03-25 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 22:41 Kirill A. Shutemov
2015-03-25 22:45 ` Hugh Dickins
2015-03-25 22:48 ` Hugh Dickins [this message]
2015-03-25 22:56 ` Kirill A. Shutemov
2015-03-25 23:09 ` Hugh Dickins
2015-03-26 15:27 Kirill A. Shutemov
2015-03-26 15:52 ` 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=alpine.LSU.2.11.1503251545510.4490@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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