Re: [PATCH][0/8] (Targeting 2.6.17) Posix memory locking and balanced mlock-LRU semantic

On Mon, 20 Mar 2006, Christoph Lameter wrote:

> The result of not scanning mlocked pages will be that mmapped files will 
> not be updated unless either the process terminates or msync() is called.

That's ok.  Light swapping on a system with non-mlocked
mmapped pages has the same result, since we won't scan
mapped pages most of the time...

-- 
All Rights Reversed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH][0/8] (Targeting 2.6.17) Posix memory locking and balanced mlock-LRU semantic
    • From: "Stone Wang" <[email protected]>
  • Re: [PATCH][0/8] (Targeting 2.6.17) Posix memory locking and balanced mlock-LRU semantic
    • From: Christoph Lameter <[email protected]>

• Prev by Date: [PATCH 8 of 18] ipath - sysfs and ipathfs support for core driver
• Next by Date: [PATCH 16 of 18] ipath - misc infiniband code, part 2
• Previous by thread: Re: [PATCH][0/8] (Targeting 2.6.17) Posix memory locking and balanced mlock-LRU semantic
• Next by thread: Re: [PATCH][0/8] (Targeting 2.6.17) Posix memory locking and balanced mlock-LRU semantic
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]