Robin Holt <[email protected]> wrote:
>
> This patch introduces a tmpfs mount option which allows specifying a
> memory policy and a second option to specify the nodelist for that policy.
> With the default policy, tmpfs will behave as it does today. This patch
> adds support for preferred, bind, and interleave policies.
>
> The default policy will cause pages to be added to tmpfs files on the
> node which is doing the writing. Some jobs expect a single process to
> create and manage the tmpfs files. This results in a node which has a
> significantly reduced number of free pages.
>
> With this patch, the administrator can specify the policy and nodes for
> that policy where they would prefer allocations.
Confused. Is this for applications which cannot be taught to use the
mempolicy API?
-
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/
[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]
