lkml.org 
[lkml]   [2001]   [Nov]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Google's mm problem - not reproduced on 2.4.13
Date
In article <20011102222754.2366f1f5.skraw@ithnet.com>,
Stephan von Krawczynski <skraw@ithnet.com> wrote:
>
>> - /* Don't swap out areas which are locked down */
>> - if (vma->vm_flags & (VM_LOCKED|VM_RESERVED))
>> + /* Don't swap out areas which are reserved */
>> + if (vma->vm_flags & VM_RESERVED)
>> return count;
>
>Although I agree what you said about differences of old and new VM, I believe
>the above was not really what Ben intended to do by mlocking. I mean, you swap
>them out right now, or not?

Not. See where I added the VM_LOCKED test - deep down in the page-out
code it will decide that a VM_LOCKED page is always accessed, and will
move it to the active list instead of swapping it out.

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:12    [W:0.038 / U:1.440 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site