lkml.org 
[lkml]   [2009]   [May]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC PATCH 0/4]: affinity-on-next-touch
Andi Kleen wrote:
> Stefan Lankes <lankes@lfbs.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



\
 
 \ /
  Last update: 2009-05-11 15:35    [W:0.222 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site