linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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).
Date: Fri, 13 Jan 2006 12:23:49 -0800	[thread overview]
Message-ID: <20060113122349.5c367e05.akpm@osdl.org> (raw)
In-Reply-To: <20060113162119.GF19156@lnx-holt.americas.sgi.com>

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?

  reply	other threads:[~2006-01-13 20:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13 16:04 [Patch] Add tmpfs options for memory placement policies Robin Holt
2006-01-13 16:21 ` [Patch] Add tmpfs options for memory placement policies (Resend with corrected addresses) Robin Holt
2006-01-13 20:23   ` Andrew Morton [this message]
2006-01-13 21:25     ` Brent Casavant
2006-01-14  7:04       ` Hugh Dickins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060113122349.5c367e05.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ak@suse.de \
    --cc=bcasavan@americas.sgi.com \
    --cc=holt@sgi.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).