From: Matthew Wilcox <willy@infradead.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-mm@kvack.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Christoph Lameter <cl@linux.com>,
Matthew Wilcox <mawilcox@microsoft.com>
Subject: Re: [PATCH 7/8] mm: Document how to use struct page
Date: Tue, 19 Dec 2017 05:07:03 -0800 [thread overview]
Message-ID: <20171219130703.GC13680@bombadil.infradead.org> (raw)
In-Reply-To: <20171219095927.GF2787@dhcp22.suse.cz>
On Tue, Dec 19, 2017 at 10:59:27AM +0100, Michal Hocko wrote:
> On Sat 16-12-17 08:44:24, Matthew Wilcox wrote:
> > From: Matthew Wilcox <mawilcox@microsoft.com>
> >
> > Be really explicit about what bits / bytes are reserved for users that
> > want to store extra information about the pages they allocate.
> >
> > Signed-off-by: Matthew Wilcox <mawilcox@microsoft.com>
>
> I think that struct page would benefit from more documentation. But this
> looks good to me already. Hugetlb pages abuse some fields in page[1],
> page_is_pfmemalloc is abusing index and there are probably more. It
> would be great to have all those described at the single place. I will
> update hugetlb part along with my recent patches which are in RFC right
> now. Maybe a good project for somebody who wants to learn a lot about MM
> and interaction with other subsystems (or maybe not ;))
>
> Acked-by: Michal Hocko <mhocko@suse.com>
Thanks! Completely agree that what I have written here so far reflects
my own limited understanding of the MM. Kirill's been really patient
with teaching me some of the things I didn't know, so it seems only fair
to write down what I do know so it doesn't have to be explained to the
next eager developer who isn't steeped in the mythos of the MM system.
I'm also teaching myself more about ReStructuredText, and to that end I've
started to document all these pages side-by-side in a table. Here's what
I have so far (and I know it's incomplete):
+---+-----------+-----------+--------------+----------+--------+--------------+
| B | slab | pagecache | tail 1 | anon | tail 2 | hugetlb |
+===+===========+===========+==============+==========+========+==============+
| 0 | flags |
+---+ |
| 4 | |
+---+-----------+-----------+--------------+----------+--------+--------------+
| 8 | s_mem | mapping | cmp_mapcount | anon_vma | defer | mapping |
+---+ | +--------------+ | list | |
|12 | | | | | | |
+---+-----------+-----------+--------------+----------+ +--------------+
|16 | freelist | index | | index |
+---+ | | | (shifted) |
|20 | | | | |
+---+-----------+-------------------------------------+--------+--------------+
|24 | counters | mapcount |
+---+ +-----------+--------------+----------+--------+--------------+
|28 | | refcount | | | | refcount |
+---+-----------+-----------+--------------+----------+--------+--------------+
|32 | next | lru | cmpd_head | |
+---+ | | +----------------------------------+
|36 | | | | |
+---+-----------+ +--------------+----------------------------------+
|40 | pages | | dtor / order | |
+---+-----------+ +--------------+----------------------------------+
|44 | pobjects | | | |
+---+-----------+-----------+--------------+----------------------------------+
|48 | slb_cache | private | | |
+---+ | +--------------+----------------------------------+
|52 | | | | |
+---+-----------+-----------+--------------+----------------------------------+
Obviously it's simplified -- no mention of slub's use of rcu_head; no
column for page table allocations; I left off the mem_cgroup, virtual
and last_cpupid possibilities (intentionally); I don't know much about
anonymous pages yet; no mention of KSM pages; hugetlb is still mostly
a mystery to me.
I haven't even run it through an RST parser yet to see if this is a good
table ;-)
Once it is good, then I'll duplicate it for 32-bit.
--
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:[~2017-12-19 13:07 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 16:44 [PATCH 0/8] Restructure struct page Matthew Wilcox
2017-12-16 16:44 ` [PATCH 1/8] mm: Align struct page more aesthetically Matthew Wilcox
2017-12-18 15:22 ` Michal Hocko
2017-12-19 14:58 ` Christopher Lameter
2017-12-16 16:44 ` [PATCH 2/8] mm: De-indent struct page Matthew Wilcox
2017-12-18 15:36 ` Michal Hocko
2017-12-18 16:19 ` Matthew Wilcox
2017-12-18 20:49 ` Michal Hocko
2017-12-18 21:44 ` Matthew Wilcox
2017-12-19 14:59 ` Christopher Lameter
2017-12-16 16:44 ` [PATCH 3/8] mm: Remove misleading alignment claims Matthew Wilcox
2017-12-19 15:01 ` Christopher Lameter
2017-12-16 16:44 ` [PATCH 4/8] mm: Improve comment on page->mapping Matthew Wilcox
2017-12-19 8:02 ` Michal Hocko
2017-12-19 15:48 ` Christopher Lameter
2017-12-16 16:44 ` [PATCH 5/8] mm: Introduce _slub_counter_t Matthew Wilcox
2017-12-19 8:07 ` Michal Hocko
2017-12-19 12:46 ` Matthew Wilcox
2017-12-19 13:01 ` Michal Hocko
2017-12-20 16:19 ` Matthew Wilcox
2017-12-21 17:03 ` Christopher Lameter
2017-12-16 16:44 ` [PATCH 6/8] mm: Store compound_dtor / compound_order as bytes Matthew Wilcox
2017-12-19 8:19 ` Michal Hocko
2017-12-19 12:49 ` Matthew Wilcox
2017-12-16 16:44 ` [PATCH 7/8] mm: Document how to use struct page Matthew Wilcox
2017-12-16 17:47 ` Randy Dunlap
2017-12-17 1:15 ` Matthew Wilcox
2017-12-19 9:59 ` Michal Hocko
2017-12-19 13:07 ` Matthew Wilcox [this message]
2017-12-19 13:43 ` Kirill A. Shutemov
2017-12-19 13:48 ` Michal Hocko
2017-12-19 15:53 ` Christopher Lameter
2017-12-19 15:56 ` Kirill A. Shutemov
2017-12-19 16:12 ` Matthew Wilcox
2017-12-16 16:44 ` [PATCH 8/8] mm: Remove reference to PG_buddy Matthew Wilcox
2017-12-19 10:02 ` Michal Hocko
2017-12-19 15:53 ` Christopher Lameter
2017-12-17 13:06 ` [PATCH 0/8] Restructure struct page Kirill A. Shutemov
-- strict thread matches above, loose matches on Subject: below --
2017-12-20 15:52 Matthew Wilcox
2017-12-20 15:52 ` [PATCH 7/8] mm: Document how to use " Matthew Wilcox
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=20171219130703.GC13680@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=cl@linux.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=mawilcox@microsoft.com \
--cc=mhocko@kernel.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).