linux-kernel - Re: [PATCH 03/13] mm: meminit: Only set page reserved in the memblock region

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: <20150427154327.f7326dc16649ae402b5b5dd3@linux-foundation.org>
Date:	Mon, 27 Apr 2015 15:43:27 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Mel Gorman <mgorman@...e.de>
Cc:	Linux-MM <linux-mm@...ck.org>, Nathan Zimmer <nzimmer@....com>,
	Dave Hansen <dave.hansen@...el.com>,
	Waiman Long <waiman.long@...com>,
	Scott Norton <scott.norton@...com>,
	Daniel J Blueman <daniel@...ascale.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 03/13] mm: meminit: Only set page reserved in the
 memblock region

On Thu, 23 Apr 2015 11:33:06 +0100 Mel Gorman <mgorman@...e.de> wrote:

> From: Nathan Zimmer <nzimmer@....com>
> 
> Currently we when we initialze each page struct is set as reserved upon
> initialization.

Hard to parse.  I changed it to "Currently each page struct is set as
reserved upon initialization".

>  This changes to starting with the reserved bit clear and
> then only setting the bit in the reserved region.

For what reason?

A code comment over reserve_bootmem_region() would be a good way
to answer that.
--
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/