linux-kernel - Re: [RFCv2] mm: page allocation for less fragmentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <551325A6.5000405@lge.com>
Date:	Thu, 26 Mar 2015 06:16:22 +0900
From:	Gioh Kim <gioh.kim@....com>
To:	Mel Gorman <mgorman@...e.de>
CC:	akpm@...ux-foundation.org, riel@...hat.com, hannes@...xchg.org,
	rientjes@...gle.com, vdavydov@...allels.com,
	iamjoonsoo.kim@....com, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, gunho.lee@....com
Subject: Re: [RFCv2] mm: page allocation for less fragmentation



2015-03-25 오후 7:56에 Mel Gorman 이(가) 쓴 글:
> 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?

It's not related to CMA and MOVABLE zone.
It's for compaction and anti-fragmentation for any zone.


>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/