From: Vlastimil Babka <vbabka@suse.cz>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
akpm@linux-foundation.org
Cc: aarcange@redhat.com, linux-mm@kvack.org
Subject: Re: [PATCH] mm/page_alloc.c: drop dead destroy_compound_page()
Date: Tue, 06 Jan 2015 18:43:49 +0100 [thread overview]
Message-ID: <54AC1ED5.2050101@suse.cz> (raw)
In-Reply-To: <1420458382-161038-1-git-send-email-kirill.shutemov@linux.intel.com>
On 01/05/2015 12:46 PM, Kirill A. Shutemov wrote:
> The only caller is __free_one_page(). By the time we should have
> page->flags to be cleared already:
>
> - for 0-order pages though PCP list:
Can there even be a 0-order compound page? I guess not, so this is just confusing?
Otherwise it seems like you are right and it's a dead code to be removed. I
tried to check history to see when it was actually needed, but seems it predates
git.
Acked-by: Vlastimil Babka <vbabka@suse.cz>
> free_hot_cold_page()
> free_pages_prepare()
> free_pages_check()
> page->flags &= ~PAGE_FLAGS_CHECK_AT_PREP;
> <put the page to PCP list>
>
> free_pcppages_bulk()
> page = <withdraw pages from PCP list>
> __free_one_page(page)
>
> - for non-0-order pages:
> __free_pages_ok()
> free_pages_prepare()
> free_pages_check()
> page->flags &= ~PAGE_FLAGS_CHECK_AT_PREP;
> free_one_page()
> __free_one_page()
>
> So there's no way PageCompound() will return true in __free_one_page().
> Let's remove dead destroy_compound_page() and put assert for page->flags
> there instead.
>
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> ---
> mm/page_alloc.c | 35 +----------------------------------
> 1 file changed, 1 insertion(+), 34 deletions(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 1bb65e6f48dd..5e75380dacab 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -381,36 +381,6 @@ void prep_compound_page(struct page *page, unsigned long order)
> }
> }
>
> -/* update __split_huge_page_refcount if you change this function */
> -static int destroy_compound_page(struct page *page, unsigned long order)
> -{
> - int i;
> - int nr_pages = 1 << order;
> - int bad = 0;
> -
> - if (unlikely(compound_order(page) != order)) {
> - bad_page(page, "wrong compound order", 0);
> - bad++;
> - }
> -
> - __ClearPageHead(page);
> -
> - for (i = 1; i < nr_pages; i++) {
> - struct page *p = page + i;
> -
> - if (unlikely(!PageTail(p))) {
> - bad_page(page, "PageTail not set", 0);
> - bad++;
> - } else if (unlikely(p->first_page != page)) {
> - bad_page(page, "first_page not consistent", 0);
> - bad++;
> - }
> - __ClearPageTail(p);
> - }
> -
> - return bad;
> -}
> -
> static inline void prep_zero_page(struct page *page, unsigned int order,
> gfp_t gfp_flags)
> {
> @@ -613,10 +583,7 @@ static inline void __free_one_page(struct page *page,
> int max_order = MAX_ORDER;
>
> VM_BUG_ON(!zone_is_initialized(zone));
> -
> - if (unlikely(PageCompound(page)))
> - if (unlikely(destroy_compound_page(page, order)))
> - return;
> + VM_BUG_ON_PAGE(page->flags & PAGE_FLAGS_CHECK_AT_PREP, page);
>
> VM_BUG_ON(migratetype == -1);
> if (is_migrate_isolate(migratetype)) {
>
--
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-01-06 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 11:46 [PATCH] mm/page_alloc.c: drop dead destroy_compound_page() Kirill A. Shutemov
2015-01-06 17:43 ` Vlastimil Babka [this message]
2015-01-06 18:29 ` Kirill A. Shutemov
2015-01-07 21:40 ` Andrew Morton
2015-01-08 14:10 ` Kirill A. Shutemov
2015-01-10 0:24 ` Andrew Morton
2015-01-10 0:41 ` Kirill A. Shutemov
2015-01-10 1:06 ` Andrew Morton
2015-01-10 1:15 ` 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=54AC1ED5.2050101@suse.cz \
--to=vbabka@suse.cz \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.