From: Mel Gorman <mel@csn.ul.ie>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Christoph Lameter <cl@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] page-allocator: Maintain rolling count of pages to free from the PCP
Date: Fri, 28 Aug 2009 14:36:31 +0100 [thread overview]
Message-ID: <20090828133631.GF5054@csn.ul.ie> (raw)
In-Reply-To: <1251464564.8514.3.camel@penberg-laptop>
On Fri, Aug 28, 2009 at 04:02:44PM +0300, Pekka Enberg wrote:
> Hi Mel,
>
> On Fri, 2009-08-28 at 13:57 +0100, Mel Gorman wrote:
> > On Fri, Aug 28, 2009 at 03:16:34PM +0300, Pekka Enberg wrote:
> > > Hi Mel,
> > >
> > > On Fri, Aug 28, 2009 at 11:44 AM, Mel Gorman<mel@csn.ul.ie> wrote:
> > > > - page = list_entry(list->prev, struct page, lru);
> > > > - /* have to delete it as __free_one_page list manipulates */
> > > > - list_del(&page->lru);
> > > > - trace_mm_page_pcpu_drain(page, 0, migratetype);
> > > > - __free_one_page(page, zone, 0, migratetype);
> > > > + do {
> > > > + page = list_entry(list->prev, struct page, lru);
> > > > + /* must delete as __free_one_page list manipulates */
> > > > + list_del(&page->lru);
> > > > + __free_one_page(page, zone, 0, migratetype);
> > > > + trace_mm_page_pcpu_drain(page, 0, migratetype);
> > >
> > > This calls trace_mm_page_pcpu_drain() *after* __free_one_page(). It's
> > > probably not a good idea as __free_one_page() can alter the struct
> > > page in various ways.
> > >
> >
> > While true, does it alter the struct page in any way that matters?
>
> Page flags and order are probably interesting for tracing?
>
This is PCPU draining. The flags are already clear of any values of interest
and the order is always 0. I can follow up a fix-patch that reverses it just
in case but I don't think it makes a major difference?
--
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-08-28 13:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 8:44 [PATCH 0/3] Reduce searching in the page allocator fast-path Mel Gorman
2009-08-28 8:44 ` [PATCH 1/2] page-allocator: Split per-cpu list into one-list-per-migrate-type Mel Gorman
2009-08-28 11:52 ` Minchan Kim
2009-08-28 12:00 ` Minchan Kim
2009-08-28 12:56 ` Mel Gorman
2009-08-28 13:46 ` Minchan Kim
2009-08-28 8:44 ` [PATCH 2/2] page-allocator: Maintain rolling count of pages to free from the PCP Mel Gorman
2009-08-28 12:16 ` Pekka Enberg
2009-08-28 12:57 ` Mel Gorman
2009-08-28 13:02 ` Pekka Enberg
2009-08-28 13:36 ` Mel Gorman [this message]
2009-08-28 13:43 ` Pekka Enberg
2009-08-28 13:49 ` Minchan Kim
2009-08-28 15:04 ` Minchan Kim
2009-08-31 12:11 ` Mel Gorman
2009-08-28 8:47 ` [PATCH 0/3] Reduce searching in the page allocator fast-path 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=20090828133631.GF5054@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--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).