From: Vlastimil Babka <vbabka@suse.cz>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>,
David Rientjes <rientjes@google.com>,
Rik van Riel <riel@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] mm/page_alloc: expands broken freepage to proper buddy list when steal
Date: Wed, 10 Dec 2014 10:55:02 +0100 [thread overview]
Message-ID: <54881876.70309@suse.cz> (raw)
In-Reply-To: <20141210063840.GC13371@js1304-P5Q-DELUXE>
On 12/10/2014 07:38 AM, Joonsoo Kim wrote:
> On Mon, Dec 08, 2014 at 10:29:44AM +0100, Vlastimil Babka wrote:
>> On 12/08/2014 08:16 AM, Joonsoo Kim wrote:
>>> There is odd behaviour when we steal freepages from other migratetype
>>> buddy list. In try_to_steal_freepages(), we move all freepages in
>>> the pageblock that founded freepage is belong to to the request
>>> migratetype in order to mitigate fragmentation. If the number of moved
>>> pages are enough to change pageblock migratetype, there is no problem. If
>>> not enough, we don't change pageblock migratetype and add broken freepages
>>> to the original migratetype buddy list rather than request migratetype
>>> one. For me, this is odd, because we already moved all freepages in this
>>> pageblock to the request migratetype. This patch fixes this situation to
>>> add broken freepages to the request migratetype buddy list in this case.
>>
>> I'd rather split the fix from the refactoring. And maybe my
>> description is longer, but easier to understand? (I guess somebody
>> else should judge this)
>
> Your patch is much better to understand than mine. :)
> No need to judge from somebody else.
> After your patch is merged, I will resubmit these on top of it.
Thanks. I'm doing another evaluation focusing on number of unmovable
pageblocks as Mel suggested and then resubmit with tracepoint fixed.
Vlastimil
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Vlastimil Babka <vbabka@suse.cz>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>,
David Rientjes <rientjes@google.com>,
Rik van Riel <riel@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] mm/page_alloc: expands broken freepage to proper buddy list when steal
Date: Wed, 10 Dec 2014 10:55:02 +0100 [thread overview]
Message-ID: <54881876.70309@suse.cz> (raw)
In-Reply-To: <20141210063840.GC13371@js1304-P5Q-DELUXE>
On 12/10/2014 07:38 AM, Joonsoo Kim wrote:
> On Mon, Dec 08, 2014 at 10:29:44AM +0100, Vlastimil Babka wrote:
>> On 12/08/2014 08:16 AM, Joonsoo Kim wrote:
>>> There is odd behaviour when we steal freepages from other migratetype
>>> buddy list. In try_to_steal_freepages(), we move all freepages in
>>> the pageblock that founded freepage is belong to to the request
>>> migratetype in order to mitigate fragmentation. If the number of moved
>>> pages are enough to change pageblock migratetype, there is no problem. If
>>> not enough, we don't change pageblock migratetype and add broken freepages
>>> to the original migratetype buddy list rather than request migratetype
>>> one. For me, this is odd, because we already moved all freepages in this
>>> pageblock to the request migratetype. This patch fixes this situation to
>>> add broken freepages to the request migratetype buddy list in this case.
>>
>> I'd rather split the fix from the refactoring. And maybe my
>> description is longer, but easier to understand? (I guess somebody
>> else should judge this)
>
> Your patch is much better to understand than mine. :)
> No need to judge from somebody else.
> After your patch is merged, I will resubmit these on top of it.
Thanks. I'm doing another evaluation focusing on number of unmovable
pageblocks as Mel suggested and then resubmit with tracepoint fixed.
Vlastimil
next prev parent reply other threads:[~2014-12-10 9:55 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 7:16 [PATCH 0/4] enhance compaction success rate Joonsoo Kim
2014-12-08 7:16 ` Joonsoo Kim
2014-12-08 7:16 ` [PATCH 1/4] mm/compaction: fix wrong order check in compact_finished() Joonsoo Kim
2014-12-08 7:16 ` Joonsoo Kim
2014-12-08 7:16 ` Joonsoo Kim
2014-12-08 9:06 ` Vlastimil Babka
2014-12-08 9:06 ` Vlastimil Babka
2014-12-08 7:16 ` [PATCH 2/4] mm/page_alloc: expands broken freepage to proper buddy list when steal Joonsoo Kim
2014-12-08 7:16 ` Joonsoo Kim
2014-12-08 9:29 ` Vlastimil Babka
2014-12-08 9:29 ` Vlastimil Babka
2014-12-10 6:38 ` Joonsoo Kim
2014-12-10 6:38 ` Joonsoo Kim
2014-12-10 9:55 ` Vlastimil Babka [this message]
2014-12-10 9:55 ` Vlastimil Babka
2015-01-27 7:35 ` Vlastimil Babka
2015-01-27 7:35 ` Vlastimil Babka
2015-01-27 8:34 ` Joonsoo Kim
2015-01-27 8:34 ` Joonsoo Kim
2015-01-27 8:36 ` Vlastimil Babka
2015-01-27 8:36 ` Vlastimil Babka
2014-12-08 7:16 ` [PATCH 3/4] mm/compaction: enhance compaction finish condition Joonsoo Kim
2014-12-08 7:16 ` Joonsoo Kim
2014-12-08 9:34 ` Vlastimil Babka
2014-12-08 9:34 ` Vlastimil Babka
2014-12-10 6:46 ` Joonsoo Kim
2014-12-10 6:46 ` Joonsoo Kim
2014-12-08 7:16 ` [PATCH 4/4] mm/compaction: stop the isolation when we isolate enough freepage Joonsoo Kim
2014-12-08 7:16 ` Joonsoo Kim
2014-12-08 9:59 ` Vlastimil Babka
2014-12-08 9:59 ` Vlastimil Babka
2014-12-10 7:00 ` Joonsoo Kim
2014-12-10 7:00 ` Joonsoo Kim
2014-12-10 15:19 ` Vlastimil Babka
2014-12-10 15:19 ` Vlastimil Babka
2014-12-11 3:09 ` Joonsoo Kim
2014-12-11 3:09 ` Joonsoo Kim
2014-12-08 9:16 ` [PATCH 0/4] enhance compaction success rate Vlastimil Babka
2014-12-08 9:16 ` Vlastimil Babka
2014-12-10 6:36 ` Joonsoo Kim
2014-12-10 6:36 ` Joonsoo 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=54881876.70309@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=riel@redhat.com \
--cc=rientjes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.