From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: mel@csn.ul.ie, kosaki.motohiro@jp.fujitsu.com,
maximlevitsky@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Lee.Schermerhorn@hp.com,
penberg@cs.helsinki.fi, hannes@cmpxchg.org, jirislaby@gmail.com
Subject: Re: [PATCH] mm: Warn once when a page is freed with PG_mlocked set V2
Date: Wed, 22 Jul 2009 16:06:49 -0700 [thread overview]
Message-ID: <20090722160649.61176c61.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0907151027410.23643@gentwo.org>
On Wed, 15 Jul 2009 10:31:54 -0400 (EDT)
Christoph Lameter <cl@linux-foundation.org> wrote:
> On Wed, 15 Jul 2009, Mel Gorman wrote:
>
> > -static inline int free_pages_check(struct page *page)
> > +static inline int free_pages_check(struct page *page, int wasMlocked)
> > {
> > + WARN_ONCE(wasMlocked, KERN_WARNING
> > + "Page flag mlocked set for process %s at pfn:%05lx\n"
> > + "page:%p flags:0x%lX\n",
> > + current->comm, page_to_pfn(page),
> > + page, page->flags|__PG_MLOCKED);
> > +
> > if (unlikely(page_mapcount(page) |
>
> There is already a free_page_mlocked() that is only called if the mlock
> bit is set. Move it into there to avoid having to run two checks in the
> hot codee path?
Agreed.
This patch gratuitously adds hotpath overhead. Moving the change to be
inside those preexisting wasMlocked tests will reduce its overhead a lot.
As it stands, I'm really doubting that the patch's utility is worth its
cost.
Also, it's a bit of a figleaf, but please consider making more use of
CONFIG_DEBUG_VM (see VM_BUG_ON()).
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: mel@csn.ul.ie, kosaki.motohiro@jp.fujitsu.com,
maximlevitsky@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Lee.Schermerhorn@hp.com,
penberg@cs.helsinki.fi, hannes@cmpxchg.org, jirislaby@gmail.com
Subject: Re: [PATCH] mm: Warn once when a page is freed with PG_mlocked set V2
Date: Wed, 22 Jul 2009 16:06:49 -0700 [thread overview]
Message-ID: <20090722160649.61176c61.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0907151027410.23643@gentwo.org>
On Wed, 15 Jul 2009 10:31:54 -0400 (EDT)
Christoph Lameter <cl@linux-foundation.org> wrote:
> On Wed, 15 Jul 2009, Mel Gorman wrote:
>
> > -static inline int free_pages_check(struct page *page)
> > +static inline int free_pages_check(struct page *page, int wasMlocked)
> > {
> > + WARN_ONCE(wasMlocked, KERN_WARNING
> > + "Page flag mlocked set for process %s at pfn:%05lx\n"
> > + "page:%p flags:0x%lX\n",
> > + current->comm, page_to_pfn(page),
> > + page, page->flags|__PG_MLOCKED);
> > +
> > if (unlikely(page_mapcount(page) |
>
> There is already a free_page_mlocked() that is only called if the mlock
> bit is set. Move it into there to avoid having to run two checks in the
> hot codee path?
Agreed.
This patch gratuitously adds hotpath overhead. Moving the change to be
inside those preexisting wasMlocked tests will reduce its overhead a lot.
As it stands, I'm really doubting that the patch's utility is worth its
cost.
Also, it's a bit of a figleaf, but please consider making more use of
CONFIG_DEBUG_VM (see VM_BUG_ON()).
--
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:[~2009-07-22 23:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 12:58 [PATCH] mm: Warn once when a page is freed with PG_mlocked set V2 Mel Gorman
2009-07-15 12:58 ` Mel Gorman
2009-07-15 14:31 ` Christoph Lameter
2009-07-15 14:31 ` Christoph Lameter
2009-07-15 22:04 ` Johannes Weiner
2009-07-15 22:04 ` Johannes Weiner
2009-07-16 7:37 ` KOSAKI Motohiro
2009-07-16 7:37 ` KOSAKI Motohiro
2009-07-16 13:54 ` Christoph Lameter
2009-07-16 13:54 ` Christoph Lameter
2009-07-16 16:01 ` Johannes Weiner
2009-07-16 16:01 ` Johannes Weiner
2009-07-17 0:17 ` KOSAKI Motohiro
2009-07-17 0:17 ` KOSAKI Motohiro
2009-07-22 23:06 ` Andrew Morton [this message]
2009-07-22 23:06 ` Andrew Morton
2009-07-23 10:29 ` Mel Gorman
2009-07-23 10:29 ` Mel Gorman
2009-07-23 17:23 ` Andrew Morton
2009-07-23 17:23 ` Andrew Morton
2009-07-24 10:36 ` Mel Gorman
2009-07-24 10:36 ` Mel Gorman
2009-07-24 11:31 ` Christoph Lameter
2009-07-24 11:31 ` Christoph Lameter
2009-07-24 12:00 ` Johannes Weiner
2009-07-24 12:00 ` Johannes Weiner
2009-07-24 12:59 ` Mel Gorman
2009-07-24 12:59 ` Mel Gorman
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=20090722160649.61176c61.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Lee.Schermerhorn@hp.com \
--cc=cl@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jirislaby@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maximlevitsky@gmail.com \
--cc=mel@csn.ul.ie \
--cc=penberg@cs.helsinki.fi \
/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.