linux-kernel - Re: [RFC] memory hotremove patch take 2 [05/10] (make basic remove code)

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: <Pine.LNX.4.64.0705101108251.10002@schroedinger.engr.sgi.com>
Date:	Thu, 10 May 2007 11:09:29 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Yasunori Goto <y-goto@...fujitsu.com>
cc:	Linux Kernel ML <linux-kernel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>, Andrew Morton <akpm@...l.org>,
	Mel Gorman <mel@....ul.ie>
Subject: Re: [RFC] memory hotremove patch take 2 [05/10] (make basic remove
 code)

On Wed, 9 May 2007, Yasunori Goto wrote:

> +/*
> + * Just an easy implementation.
> + */
> +static struct page *
> +hotremove_migrate_alloc(struct page *page,
> +			unsigned long private,
> +			int **x)
> +{
> +	return alloc_page(GFP_HIGH_MOVABLE);
> +}

This would need to reflect the zone in which you are performing hot 
remove. Or is hot remove only possible in the higest 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/