linux-kernel - Re: [PATCH 2.6.21-rc1-mm1] add check_highest_zone to build_zonelists_in_zone

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

Date:	Thu, 17 May 2007 10:04:32 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Lee Schermerhorn <Lee.Schermerhorn@...com>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	akpm@...ux-foundation.org, apw@...dowen.org, clameter@....com,
	ak@...e.de, jbarnes@...tuousgeek.org, eric.whitney@...com
Subject: Re: [PATCH 2.6.21-rc1-mm1] add check_highest_zone to
 build_zonelists_in_zone_order

On Wed, 16 May 2007 15:57:39 -0400
Lee Schermerhorn <Lee.Schermerhorn@...com> wrote:

> 
> [PATCH 2.6.21-rc1-mm1] add check_highest_zone to build_zonelists_in_zone_order
> 
> We missed this in the "change zone order" series.  We need to record
> the highest populated zone, just as build_zonelists_node() does.
> Memory policies apply only to this zone.  Without this, we'll be
> applying policy to all zones, including DMA, I think.  Not having
> thought about it much, I can't claim to understand the downside of
> doing so.
> 
> Also, display selected "policy zone" during boot or reconfig
> of zonelist order, if 'NUMA.  Inquiring minds [might] want to know...
> 
> Cleanup:  remove stale comment in set_zonelist_order()
> 
> Signed-off-by:  Lee Schermerhorn <lee.schermerhorn@...com>
>
Acked-By: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>

-Kame

-
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/