linux-kernel - RE: [RFC PATCH 0/4]: affinity-on-next-touch

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, 12 Jun 2009 15:48:36 +0200
From:	Stefan Lankes <lankes@...s.rwth-aachen.de>
To:	'Brice Goglin' <Brice.Goglin@...ia.fr>
Cc:	'Andi Kleen' <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	Lee.Schermerhorn@...com, linux-numa@...r.kernel.org,
	Boris Bierbaum <boris@...s.rwth-aachen.de>
Subject: RE: [RFC PATCH 0/4]: affinity-on-next-touch

> >
> 
> MPOL_MF_LAZY is used as flag and does not specify a new policy.
> Therefore, MPOL_MF_LAZY isn't stored in a VMA. The flag is only used to
> detect that the system call mbind has to unmap these pages.
> 

In one of my previous e-mails, I wrote that Lee use the normal NUMA memory
policies. This statement was unclear. Lee's patches define no new memory
policy. He adds only a new flag. The using of mbind looks for me smarter as
the using of madvise. 

Stefan

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