linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
To: yanfei.xu@windriver.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@redhat.com>,
	 Vlastimil Babka <vbabka@suse.cz>, Linux MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mm/compaction: Rename 'start_pfn' to 'iteration_start_pfn' in compact_zone()
Date: Mon, 19 Oct 2020 10:50:53 +0200	[thread overview]
Message-ID: <CAM9Jb+iz3r3JeERmgvFeQfZ4vY7=TKtoXNEaDvmRPVAmhcyHnw@mail.gmail.com> (raw)
In-Reply-To: <20201019083632.25417-1-yanfei.xu@windriver.com>

> From: Yanfei Xu <yanfei.xu@windriver.com>
>
> There are two 'start_pfn' declared in compact_zone() which have
> different meaning. Rename the second one to 'iteration_start_pfn'
> to prevent trace_mm_compaction_end() from tracing an undesirable
> value.
>
> BTW, remove an useless semicolon.
>
> Acked-by: David Hildenbrand <david@redhat.com>
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
> Signed-off-by: Yanfei Xu <yanfei.xu@windriver.com>
> ---
> v1->v2:
> Rename 'start_pfn' to 'iteration_start_pfn' and change commit messages.
>
>  mm/compaction.c | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/mm/compaction.c b/mm/compaction.c
> index 176dcded298e..ccd27c739fd6 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -2272,7 +2272,7 @@ compact_zone(struct compact_control *cc, struct capture_control *capc)
>
>         while ((ret = compact_finished(cc)) == COMPACT_CONTINUE) {
>                 int err;
> -               unsigned long start_pfn = cc->migrate_pfn;
> +               unsigned long iteration_start_pfn = cc->migrate_pfn;
>
>                 /*
>                  * Avoid multiple rescans which can happen if a page cannot be
> @@ -2284,7 +2284,7 @@ compact_zone(struct compact_control *cc, struct capture_control *capc)
>                  */
>                 cc->rescan = false;
>                 if (pageblock_start_pfn(last_migrated_pfn) ==
> -                   pageblock_start_pfn(start_pfn)) {
> +                   pageblock_start_pfn(iteration_start_pfn)) {
>                         cc->rescan = true;
>                 }
>
> @@ -2308,8 +2308,7 @@ compact_zone(struct compact_control *cc, struct capture_control *capc)
>                         goto check_drain;
>                 case ISOLATE_SUCCESS:
>                         update_cached = false;
> -                       last_migrated_pfn = start_pfn;
> -                       ;
> +                       last_migrated_pfn = iteration_start_pfn;
>                 }
>
>                 err = migrate_pages(&cc->migratepages, compaction_alloc,

Improves readability.
Acked-by: Pankaj Gupta <pankaj.gupta.linux@gmail.com>


  reply	other threads:[~2020-10-19  8:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19  8:36 yanfei.xu
2020-10-19  8:50 ` Pankaj Gupta [this message]
2020-10-19  9:40 ` Vlastimil Babka
2020-10-19 10:29   ` Xu, Yanfei
2020-10-19 10:48     ` Vlastimil Babka
2020-10-19 11:39       ` Xu, Yanfei

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='CAM9Jb+iz3r3JeERmgvFeQfZ4vY7=TKtoXNEaDvmRPVAmhcyHnw@mail.gmail.com' \
    --to=pankaj.gupta.linux@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=vbabka@suse.cz \
    --cc=yanfei.xu@windriver.com \
    /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