linux-kernel - Re: [patch v2 3/3] mm: page_alloc: fair zone allocator policy

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>] [day] [month] [year] [list]

Date:	Mon, 5 Aug 2013 13:34:23 +0200
From:	Andrea Arcangeli <aarcange@...hat.com>
To:	Wanpeng Li <liwanp@...ux.vnet.ibm.com>
Cc:	Johannes Weiner <hannes@...xchg.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Mel Gorman <mgorman@...e.de>, Rik van Riel <riel@...riel.com>,
	Zlatko Calusic <zcalusic@...sync.net>,
	Minchan Kim <minchan@...nel.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [patch v2 3/3] mm: page_alloc: fair zone allocator policy

On Mon, Aug 05, 2013 at 06:34:56PM +0800, Wanpeng Li wrote:
> Why round robin allocator don't consume ZONE_DMA?

I guess lowmem reserve reserves it all, 4GB/256(ratio)=16MB.

The only way to relax it would be 1) to account depending on memblock
types and allow only the movable ones to bypass the lowmem reserve and
prevent a change from movable type if lowmem reserve doesn't pass, 2)
use memory migration to move the movable pages from the lower zones to
the highest zone if reclaim fails if __GFP_DMA32 or __GFP_DMA is set,
or highmem is missing on 32bit kernels. The last point involving
memory migration would work similarly to compaction but it isn't black
and white, and it would cost CPU as well. The memory used by the
simple lowmem reserve mechanism is probably not significant enough to
warrant such an effort.
--
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/