mm: improve struct page documentation

 * it to keep track of whatever it is we are using the page for at the

 * it to keep track of whatever it is we are using the page for at the

 * moment. Note that we have no way to track which tasks are using

 * moment. Note that we have no way to track which tasks are using

 * a page, though if it is a pagecache page, rmap structures can tell us

 * a page, though if it is a pagecache page, rmap structures can tell us

 * who is mapping it. If you allocate the page using alloc_pages(), you

 * who is mapping it.

 * can use some of the space in struct page for your own purposes.

 *

 *

 * Pages that were once in the page cache may be found under the RCU lock

 * If you allocate the page using alloc_pages(), you can use some of the

 * even after they have been recycled to a different purpose.  The page

 * space in struct page for your own purposes.  The five words in the main

 * cache reads and writes some of the fields in struct page to pin the

 * union are available, except for bit 0 of the first word which must be

 * page before checking that it's still in the page cache.  It is vital

 * kept clear.  Many users use this word to store a pointer to an object

 * that all users of struct page:

 * which is guaranteed to be aligned.  If you use the same storage as

 * 1. Use the first word as PageFlags.

 * page->mapping, you must restore it to NULL before freeing the page.

 * 2. Clear or preserve bit 0 of page->compound_head.  It is used as

 *

 *    PageTail for compound pages, and the page cache must not see false

 * If your page will not be mapped to userspace, you can also use the four

 *    positives.  Some users put a pointer here (guaranteed to be at least

 * bytes in the mapcount union, but you must call page_mapcount_reset()

 *    4-byte aligned), other users avoid using the field altogether.

 * before freeing it.

 * 3. page->_refcount must either not be used, or must be used in such a

 *

 *    way that other CPUs temporarily incrementing and then decrementing the

 * If you want to use the refcount field, it must be used in such a way

 * that other CPUs temporarily incrementing and then decrementing the

 * refcount does not cause problems.  On receiving the page from

 * refcount does not cause problems.  On receiving the page from

 * alloc_pages(), the refcount will be positive.

 * alloc_pages(), the refcount will be positive.

 * 4. Either preserve page->_mapcount or restore it to -1 before freeing it.

 *

 *

 * If you allocate pages of order > 0, you can use the fields in the struct

 * If you allocate pages of order > 0, you can use some of the fields

 * page associated with each page, but bear in mind that the pages may have

 * in each subpage, but you may need to restore some of their values

 * been inserted individually into the page cache, so you must use the above

 * afterwards.

 * four fields in a compatible way for each struct page.

 *

 *

 * SLUB uses cmpxchg_double() to atomically update its freelist and

 * SLUB uses cmpxchg_double() to atomically update its freelist and

 * counters.  That requires that freelist & counters be adjacent and

 * counters.  That requires that freelist & counters be adjacent and