mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
	Heesub Shin <heesub.shin@samsung.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Dongjun Shin <d.j.shin@samsung.com>,
	Sunghwan Yun <sunghwan.yun@samsung.com>,
	Mel Gorman <mgorman@suse.de>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Michal Nazarewicz <mina86@mina86.com>,
	Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	Christoph Lameter <cl@linux.com>, Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH 2/2] mm/compaction: cleanup isolate_freepages()
Date: Mon, 21 Apr 2014 12:41:46 -0700	[thread overview]
Message-ID: <20140421124146.c8beacf0d58aafff2085a461@linux-foundation.org> (raw)
In-Reply-To: <20140417000745.GF27534@bbox>

On Thu, 17 Apr 2014 09:07:45 +0900 Minchan Kim <minchan@kernel.org> wrote:

> Hi Vlastimil,
> 
> Below just nitpicks.

It seems you were ignored ;)

> >  {
> >  	struct page *page;
> > -	unsigned long high_pfn, low_pfn, pfn, z_end_pfn;
> > +	unsigned long pfn, low_pfn, next_free_pfn, z_end_pfn;
> 
> Could you add comment for each variable?
> 
> unsigned long pfn; /* scanning cursor */
> unsigned long low_pfn; /* lowest pfn free scanner is able to scan */
> unsigned long next_free_pfn; /* start pfn for scaning at next truen */
> unsigned long z_end_pfn; /* zone's end pfn */
> 
> 
> > @@ -688,11 +688,10 @@ static void isolate_freepages(struct zone *zone,
> >  	low_pfn = ALIGN(cc->migrate_pfn + 1, pageblock_nr_pages);
> >  
> >  	/*
> > -	 * Take care that if the migration scanner is at the end of the zone
> > -	 * that the free scanner does not accidentally move to the next zone
> > -	 * in the next isolation cycle.
> > +	 * Seed the value for max(next_free_pfn, pfn) updates. If there are
> > +	 * none, the pfn < low_pfn check will kick in.
> 
>        "none" what? I'd like to clear more.

I did this:

--- a/mm/compaction.c~mm-compaction-cleanup-isolate_freepages-fix
+++ a/mm/compaction.c
@@ -662,7 +662,10 @@ static void isolate_freepages(struct zon
 				struct compact_control *cc)
 {
 	struct page *page;
-	unsigned long pfn, low_pfn, next_free_pfn, z_end_pfn;
+	unsigned long pfn;	     /* scanning cursor */
+	unsigned long low_pfn;	     /* lowest pfn scanner is able to scan */
+	unsigned long next_free_pfn; /* start pfn for scaning at next round */
+	unsigned long z_end_pfn;     /* zone's end pfn */
 	int nr_freepages = cc->nr_freepages;
 	struct list_head *freelist = &cc->freepages;
 
@@ -679,8 +682,8 @@ static void isolate_freepages(struct zon
 	low_pfn = ALIGN(cc->migrate_pfn + 1, pageblock_nr_pages);
 
 	/*
-	 * Seed the value for max(next_free_pfn, pfn) updates. If there are
-	 * none, the pfn < low_pfn check will kick in.
+	 * Seed the value for max(next_free_pfn, pfn) updates. If no pages are
+	 * isolated, the pfn < low_pfn check will kick in.
 	 */
 	next_free_pfn = 0;
 
> > @@ -766,9 +765,9 @@ static void isolate_freepages(struct zone *zone,
> >  	 * so that compact_finished() may detect this
> >  	 */
> >  	if (pfn < low_pfn)
> > -		cc->free_pfn = max(pfn, zone->zone_start_pfn);
> > -	else
> > -		cc->free_pfn = high_pfn;
> > +		next_free_pfn = max(pfn, zone->zone_start_pfn);
> 
> Why we need max operation?
> IOW, what's the problem if we do (next_free_pfn = pfn)?

An answer to this would be useful, thanks.

  reply	other threads:[~2014-04-21 19:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03  8:57 [PATCH 1/2] mm/compaction: clean up unused code lines Heesub Shin
2014-04-03  8:57 ` [PATCH 2/2] mm/compaction: fix to initialize free scanner properly Heesub Shin
2014-04-07 14:46   ` Vlastimil Babka
2014-04-15  9:18     ` [PATCH 1/2] mm/compaction: make isolate_freepages start at pageblock boundary Vlastimil Babka
2014-04-15  9:18       ` [PATCH 2/2] mm/compaction: cleanup isolate_freepages() Vlastimil Babka
2014-04-16  1:53         ` Joonsoo Kim
2014-04-16 15:49         ` Rik van Riel
2014-04-17  0:07         ` Minchan Kim
2014-04-21 19:41           ` Andrew Morton [this message]
2014-04-21 21:43             ` Vlastimil Babka
2014-04-21 23:53               ` Minchan Kim
2014-04-22  6:33                 ` Vlastimil Babka
2014-04-22  6:52                   ` Minchan Kim
2014-04-22 13:17                     ` Vlastimil Babka
2014-04-23  2:58                       ` Joonsoo Kim
2014-04-23  7:30                         ` Vlastimil Babka
2014-04-23 13:54                           ` Joonsoo Kim
2014-04-23 14:31                             ` Vlastimil Babka
2014-04-25  8:29                               ` Joonsoo Kim
2014-04-29  8:40                                 ` Vlastimil Babka
2014-05-01  1:58                                 ` Michal Nazarewicz
2014-04-16  1:52       ` [PATCH 1/2] mm/compaction: make isolate_freepages start at pageblock boundary Joonsoo Kim
2014-04-16 15:47       ` Rik van Riel
2014-04-16 23:43       ` Minchan Kim
2014-04-07 14:40 ` [PATCH 1/2] mm/compaction: clean up unused code lines Vlastimil Babka

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=20140421124146.c8beacf0d58aafff2085a461@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=cl@linux.com \
    --cc=d.j.shin@samsung.com \
    --cc=heesub.shin@samsung.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mina86@mina86.com \
    --cc=minchan@kernel.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=riel@redhat.com \
    --cc=sunghwan.yun@samsung.com \
    --cc=vbabka@suse.cz \
    /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

Powered by JetHome