linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	aarcange@redhat.com, linux-mm@kvack.org
Subject: Re: [PATCH] mm/page_alloc.c: drop dead destroy_compound_page()
Date: Fri, 9 Jan 2015 17:06:42 -0800	[thread overview]
Message-ID: <20150109170642.14a01c7e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20150110004143.GA32424@node.dhcp.inet.fi>

On Sat, 10 Jan 2015 02:41:43 +0200 "Kirill A. Shutemov" <kirill@shutemov.name> wrote:

> On Fri, Jan 09, 2015 at 04:24:19PM -0800, Andrew Morton wrote:
> > On Thu,  8 Jan 2015 16:10:04 +0200 (EET) "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com> wrote:
> > 
> > > Something like this?
> > > 
> > > >From 5fd481c1c521112e9cea407f5a2644c9f93d0e14 Mon Sep 17 00:00:00 2001
> > > From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
> > > Date: Thu, 8 Jan 2015 15:59:23 +0200
> > > Subject: [PATCH] mm: more checks on free_pages_prepare() for tail pages
> > > 
> > > Apart form being dead, destroy_compound_page() did some potentially
> > > useful checks. Let's re-introduce them in free_pages_prepare(), where
> > > they can be acctually triggered.
> > > 
> > > compound_order() assert is already in free_pages_prepare(). We have few
> > > checks for tail pages left.
> > > 
> > 
> > I'm thinking we avoid the overhead unless CONFIG_DEBUG_VM?
> 
> That's why there's "if (!IS_ENABLED(CONFIG_DEBUG_VM))". Is it wrong in
> some way?
> I didn't check, but I assume compiler is smart enough to get rid of
> free_tail_pages_check() if CONFIG_DEBUG_VM is not defined. No?

doh, OK.  I updated the
mm-more-checks-on-free_pages_prepare-for-tail-pages.patch changelog to
reflect this and did

--- a/mm/page_alloc.c~mm-more-checks-on-free_pages_prepare-for-tail-pages-fix
+++ a/mm/page_alloc.c
@@ -764,19 +764,18 @@ static void free_one_page(struct zone *z
 	spin_unlock(&zone->lock);
 }
 
-static int free_tail_pages_check(struct page *head_page, struct page *page)
+static void free_tail_pages_check(struct page *head_page, struct page *page)
 {
 	if (!IS_ENABLED(CONFIG_DEBUG_VM))
-		return 0;
+		return;
 	if (unlikely(!PageTail(page))) {
 		bad_page(page, "PageTail not set", 0);
-		return 1;
+		return;
 	}
 	if (unlikely(page->first_page != head_page)) {
 		bad_page(page, "first_page not consistent", 0);
-		return 1;
+		return;
 	}
-	return 0;
 }
 
 static bool free_pages_prepare(struct page *page, unsigned int order)
_

--
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>

  reply	other threads:[~2015-01-10  1:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 11:46 Kirill A. Shutemov
2015-01-06 17:43 ` Vlastimil Babka
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 [this message]
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=20150109170642.14a01c7e.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aarcange@redhat.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kirill@shutemov.name \
    --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