linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Gioh Kim <gioh.kim@lge.com>
Cc: akpm@linux-foundation.org, vbabka@suse.cz,
	iamjoonsoo.kim@lge.com, mgorman@suse.de, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, gunho.lee@lge.com
Subject: Re: [PATCH] mm/compaction: reset compaction scanner positions
Date: Mon, 23 Mar 2015 16:16:21 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.10.1503231613320.24576@chino.kir.corp.google.com> (raw)
In-Reply-To: <1426939106-30347-1-git-send-email-gioh.kim@lge.com>

On Sat, 21 Mar 2015, Gioh Kim wrote:

> When the compaction is activated via /proc/sys/vm/compact_memory
> it would better scan the whole zone.
> And some platform, for instance ARM, has the start_pfn of a zone is zero.
> Therefore the first try to compaction via /proc doesn't work.
> It needs to force to reset compaction scanner position at first.
> 
> Signed-off-by: Gioh Kim <gioh.kim@lge.c>

That shouldn't be a valid email address.

> Acked-by: Vlastimil Babka <vbabka@suse.cz>

Acked-by: David Rientjes <rientjes@google.com>

I was thinking that maybe this would be better handled as part of the 
comapct_zone() logic, i.e. set cc->free_pfn and cc->migrate_pfn based on a 
helper function that understands cc->order == -1 should compact the entire 
zone.  However, after scanning the entire zone as a result of this write, 
the existing cached pfns probably don't matter anymore.  So this seems 
fine.

--
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>

  reply	other threads:[~2015-03-23 23:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-21 11:58 Gioh Kim
2015-03-23 23:16 ` David Rientjes [this message]
2015-03-24  1:23   ` Gioh Kim

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=alpine.DEB.2.10.1503231613320.24576@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=gioh.kim@lge.com \
    --cc=gunho.lee@lge.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --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