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]
Date:	Fri, 11 May 2007 10:05:46 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Christoph Lameter <clameter@....com>
Cc:	y-goto@...fujitsu.com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, akpm@...l.org, mel@....ul.ie
Subject: Re: [RFC] memory hotremove patch take 2 [05/10] (make basic remove
 code)

On Thu, 10 May 2007 11:09:29 -0700 (PDT)
Christoph Lameter <clameter@....com> wrote:

> 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?
> 
No. We'll allow hot remove in any zone-type.
My old patchest didn't include Mel-san's page grouping and just had
ZONE_MOVABLE, so I wrote this. Reflecting migration target's zone here
is reasobanle. 

Anyway, I think we'll need more complicated function here.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ