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:	Mon, 11 May 2009 15:32:01 +0200
From:	Brice Goglin <Brice.Goglin@...ia.fr>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Stefan Lankes <lankes@...s.rwth-aachen.de>,
	linux-kernel@...r.kernel.org, Lee.Schermerhorn@...com,
	linux-numa@...r.kernel.org
Subject: Re: [RFC PATCH 0/4]: affinity-on-next-touch

Andi Kleen wrote:
> Stefan Lankes <lankes@...s.rwth-aachen.de> writes:
>   
>> [Patch 1/4]: Extend the system call madvise with a new parameter
>> MADV_ACCESS_LWP (the same as used in Solaris). The specified memory area
>>     
>
> Linux does NUMA memory policies in mbind(), not madvise()
> Also if there's a new NUMA policy it should be in the standard
> Linux NUMA memory policy frame work, not inventing a new one
>   

Marking a buffer as "migrate-on-next-touch" is very different from
setting a NUMA policy. Migrate-on-next-touch a temporary flag that is
cleared on the next-touch. It's cleared per page, not per area or
whatever. So marking a VMA as "migrate-on-next-touch" doesn't make much
sense since some pages could already have been migrated (and brought
back to their usual state) while some other are still marked as
migrate-on-next-touch.

Brice

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