linux-kernel - Re: [PATCH] Break out memory initialisation code from page_alloc.c to mem

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

Message-Id: <20061129131448.b5761339.akpm@osdl.org>
Date:	Wed, 29 Nov 2006 13:14:48 -0800
From:	Andrew Morton <akpm@...l.org>
To:	mel@...net.ie (Mel Gorman)
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Break out memory initialisation code from page_alloc.c
 to mem_init.c

On Wed, 29 Nov 2006 18:00:47 +0000
mel@...net.ie (Mel Gorman) wrote:

> page_alloc.c contains a large amount of memory initialisation code which
> obscures the purpose of the file. This patch breaks out the initialisation
> code into a separate file to make page_alloc.c a bit easier to read.
> 
> This is a repost from a long time ago.  At the time it was last posted,
> there was too much churn in page_alloc.c and it was put on the back-burner.
> However, there is still a lot going on in page_alloc.c so the time still
> might not be right.

yeah, it spits a 58k reject already.  There's basically never a good time for this,
but the best time is around 2.6.x-rc1.
-
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/