From: Mel Gorman <mgorman@suse.de>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Vlastimil Babka <vbabka@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH 1/3] mm/page_alloc: don't break highest order freepage if steal
Date: Mon, 27 Apr 2015 09:08:50 +0100 [thread overview]
Message-ID: <20150427080850.GF2449@suse.de> (raw)
In-Reply-To: <1430119421-13536-1-git-send-email-iamjoonsoo.kim@lge.com>
On Mon, Apr 27, 2015 at 04:23:39PM +0900, Joonsoo Kim wrote:
> When we steal whole pageblock, we don't need to break highest order
> freepage. Perhaps, there is small order freepage so we can use it.
>
The reason why the largest block is taken is to reduce the probability
there will be another fallback event in the near future. Early on, there
were a lot of tests conducted to measure the number of external fragmenting
events and take steps to reduce them. Stealing the largest highest order
freepage was one of those steps.
--
Mel Gorman
SUSE Labs
--
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: Mel Gorman <mgorman@suse.de>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Vlastimil Babka <vbabka@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH 1/3] mm/page_alloc: don't break highest order freepage if steal
Date: Mon, 27 Apr 2015 09:08:50 +0100 [thread overview]
Message-ID: <20150427080850.GF2449@suse.de> (raw)
In-Reply-To: <1430119421-13536-1-git-send-email-iamjoonsoo.kim@lge.com>
On Mon, Apr 27, 2015 at 04:23:39PM +0900, Joonsoo Kim wrote:
> When we steal whole pageblock, we don't need to break highest order
> freepage. Perhaps, there is small order freepage so we can use it.
>
The reason why the largest block is taken is to reduce the probability
there will be another fallback event in the near future. Early on, there
were a lot of tests conducted to measure the number of external fragmenting
events and take steps to reduce them. Stealing the largest highest order
freepage was one of those steps.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2015-04-27 8:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 7:23 [PATCH 1/3] mm/page_alloc: don't break highest order freepage if steal Joonsoo Kim
2015-04-27 7:23 ` Joonsoo Kim
2015-04-27 7:23 ` [PATCH 2/3] mm/page_alloc: stop fallback allocation if we already get some freepage Joonsoo Kim
2015-04-27 7:23 ` Joonsoo Kim
2015-05-12 8:36 ` Vlastimil Babka
2015-05-12 8:36 ` Vlastimil Babka
2015-05-19 7:47 ` Joonsoo Kim
2015-05-19 7:47 ` Joonsoo Kim
2015-04-27 7:23 ` [RFC PATCH 3/3] mm: support active anti-fragmentation algorithm Joonsoo Kim
2015-04-27 7:23 ` Joonsoo Kim
2015-04-27 8:29 ` Mel Gorman
2015-04-27 8:29 ` Mel Gorman
2015-04-28 7:45 ` Joonsoo Kim
2015-04-28 7:45 ` Joonsoo Kim
2015-05-12 9:01 ` Vlastimil Babka
2015-05-12 9:01 ` Vlastimil Babka
2015-05-19 8:04 ` Joonsoo Kim
2015-05-19 8:04 ` Joonsoo Kim
2015-04-27 8:08 ` Mel Gorman [this message]
2015-04-27 8:08 ` [PATCH 1/3] mm/page_alloc: don't break highest order freepage if steal Mel Gorman
2015-04-27 8:42 ` Joonsoo Kim
2015-04-27 8:42 ` Joonsoo Kim
2015-05-12 7:57 ` Vlastimil Babka
2015-05-12 7:57 ` Vlastimil Babka
2015-05-12 7:51 ` Vlastimil Babka
2015-05-12 7:51 ` Vlastimil Babka
2015-05-12 7:54 ` Vlastimil Babka
2015-05-12 7:54 ` Vlastimil Babka
2015-05-19 7:44 ` Joonsoo Kim
2015-05-19 7:44 ` Joonsoo Kim
2015-05-19 7:44 ` Joonsoo Kim
2015-05-19 7:44 ` 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=20150427080850.GF2449@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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 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.