From: Dave Hansen <dave.hansen@intel.com>
To: Matthew Wilcox <willy@infradead.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Cc: linux-mm@kvack.org, Matthew Wilcox <mawilcox@microsoft.com>
Subject: Re: [PATCH v2] mm: Split page_type out from _map_count
Date: Fri, 9 Feb 2018 10:43:19 -0800 [thread overview]
Message-ID: <7c5414ce-fece-b908-bebc-22fa15fc783c@intel.com> (raw)
In-Reply-To: <20180209152848.GF16666@bombadil.infradead.org>
On 02/09/2018 07:28 AM, Matthew Wilcox wrote:
> union {
> + /*
> + * If the page is neither PageSlab nor PageAnon, the value
> + * stored here may help distinguish it from page cache pages.
> + * See page-flags.h for a list of page types which are
> + * currently stored here.
> + */
> + unsigned int page_type;
> +
> _slub_counter_t counters;
> unsigned int active; /* SLAB */
> struct { /* SLUB */
> @@ -107,11 +115,6 @@ struct page {
> /*
> * Count of ptes mapped in mms, to show when
> * page is mapped & limit reverse map searches.
> - *
> - * Extra information about page type may be
> - * stored here for pages that are never mapped,
> - * in which case the value MUST BE <= -2.
> - * See page-flags.h for more details.
> */
> atomic_t _mapcount;
Are there any straightforward rules that we can enforce here? For
instance, if you are using "page_type", you can never have PG_lru set.
Not that we have done this at all for 'struct page' historically, it
would be really convenient to have a clear definition for when
"page_type" is valid vs. "_mapcount".
--
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:[~2018-02-09 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 21:30 [PATCH] " Matthew Wilcox
2018-02-09 10:51 ` Kirill A. Shutemov
2018-02-09 13:49 ` Matthew Wilcox
2018-02-09 15:28 ` [PATCH v2] " Matthew Wilcox
2018-02-09 18:43 ` Dave Hansen [this message]
2018-02-09 19:04 ` Christopher Lameter
2018-02-09 19:28 ` Matthew Wilcox
2018-02-10 5:00 ` [PATCH] " kbuild test robot
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=7c5414ce-fece-b908-bebc-22fa15fc783c@intel.com \
--to=dave.hansen@intel.com \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.org \
--cc=mawilcox@microsoft.com \
--cc=willy@infradead.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