From: Mel Gorman <mel@csn.ul.ie>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Lameter <cl@linux-foundation.org>,
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: Thu, 23 Jul 2009 11:29:39 +0100 [thread overview]
Message-ID: <20090723102938.GA27731@csn.ul.ie> (raw)
In-Reply-To: <20090722160649.61176c61.akpm@linux-foundation.org>
On Wed, Jul 22, 2009 at 04:06:49PM -0700, Andrew Morton wrote:
> 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.
>
It adds code duplication then, one of which is in a fast path.
> As it stands, I'm really doubting that the patch's utility is worth its
> cost.
>
I'm happy to let this one drop. It seemed like it would be nice for debugging
while there are still corner cases where mlocked pages are getting freed
instead of torn down but we already account for that situation occuring. While
I think it'll be tricky to spot, it's probably preferable to having warnings
spew out onto dmesg.
> Also, it's a bit of a figleaf, but please consider making more use of
> CONFIG_DEBUG_VM (see VM_BUG_ON()).
>
In this particular case, I doubted that DEBUG_VM would be set on
machines that were triggering the mlock corner case but yeah, this does
look more like a DEBUG_VM than a production thing.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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-23 10:29 UTC|newest]
Thread overview: 14+ 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 14:31 ` Christoph Lameter
2009-07-15 22:04 ` Johannes Weiner
2009-07-16 7:37 ` KOSAKI Motohiro
2009-07-16 13:54 ` Christoph Lameter
2009-07-16 16:01 ` Johannes Weiner
2009-07-17 0:17 ` KOSAKI Motohiro
2009-07-22 23:06 ` Andrew Morton
2009-07-23 10:29 ` Mel Gorman [this message]
2009-07-23 17:23 ` Andrew Morton
2009-07-24 10:36 ` Mel Gorman
2009-07-24 11:31 ` Christoph Lameter
2009-07-24 12:00 ` Johannes Weiner
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=20090723102938.GA27731@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--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=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 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).