From: Mel Gorman <mgorman@suse.de>
To: Gioh Kim <gioh.kim@lge.com>
Cc: akpm@linux-foundation.org, riel@redhat.com, hannes@cmpxchg.org,
rientjes@google.com, vdavydov@parallels.com,
iamjoonsoo.kim@lge.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, gunho.lee@lge.com
Subject: Re: [RFCv2] mm: page allocation for less fragmentation
Date: Wed, 25 Mar 2015 10:56:40 +0000 [thread overview]
Message-ID: <20150325105640.GI4701@suse.de> (raw)
In-Reply-To: <1427251155-12322-1-git-send-email-gioh.kim@lge.com>
On Wed, Mar 25, 2015 at 11:39:15AM +0900, Gioh Kim wrote:
> My driver allocates more than 40MB pages via alloc_page() at a time and
> maps them at virtual address. Totally it uses 300~400MB pages.
>
> If I run a heavy load test for a few days in 1GB memory system, I cannot allocate even order=3 pages
> because-of the external fragmentation.
>
> I thought I needed a anti-fragmentation solution for my driver.
> But there is no allocation function that considers fragmentation.
> The compaction is not helpful because it is only for movable pages, not unmovable pages.
>
> This patch proposes a allocation function allocates only pages in the same pageblock.
>
Is this not what CMA is for? Or creating a MOVABLE zone?
--
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>
next prev parent reply other threads:[~2015-03-25 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 2:39 [RFCv2] mm: page allocation for less fragmentation Gioh Kim
2015-03-25 10:56 ` Mel Gorman [this message]
2015-03-25 21:16 ` Gioh Kim
2015-03-26 10:28 ` Mel Gorman
2015-03-27 0:51 ` Gioh Kim
2015-03-25 22:16 ` Vlastimil Babka
2015-03-25 23:25 ` Gioh Kim
2015-04-01 12:05 ` 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=20150325105640.GI4701@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=gioh.kim@lge.com \
--cc=gunho.lee@lge.com \
--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=rientjes@google.com \
--cc=vdavydov@parallels.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;
as well as URLs for NNTP newsgroup(s).