Date: Fri, 13 Jan 2006 12:23:49 -0800
From: Andrew Morton <akpm@osdl.org>
To: Robin Holt <holt@sgi.com>
Cc: ak@suse.de, hugh@veritas.com, bcasavan@americas.sgi.com,
       linux-kernel@vger.kernel.org
Subject: Re: [Patch] Add tmpfs options for memory placement policies (Resend
 with corrected addresses).
Message-Id: <20060113122349.5c367e05.akpm@osdl.org>
In-Reply-To: <20060113162119.GF19156@lnx-holt.americas.sgi.com>
References: <20060113160406.GE19156@lnx-holt.americas.sgi.com>
	<20060113162119.GF19156@lnx-holt.americas.sgi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1053
Lines: 22

Robin Holt <holt@sgi.com> 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 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/