From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Brent Casavant <bcasavan@sgi.com>
Cc: Andi Kleen <ak@suse.de>,
colpatch@us.ibm.com, Hugh Dickins <hugh@veritas.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] Use MPOL_INTERLEAVE for tmpfs files
Date: Mon, 08 Nov 2004 12:57:29 -0800 [thread overview]
Message-ID: <263890000.1099947448@[10.10.2.4]> (raw)
In-Reply-To: <Pine.SGI.4.58.0411081314160.101942@kzerza.americas.sgi.com>
>> Matt has volunteered to write the mount option for this, so let's hold
>> off for a couple of days until that's done.
>
> I had the time to do this myself. Updated patch attached below.
>
> Description:
>
> This patch creates a tmpfs mount option and adds code which causes
> tmpfs allocations to be interleaved across the nodes of a NUMA machine.
> This is useful in situations where a large tmpfs file would otherwise
> consume most of the memory on a single node, forcing tasks running on
> that node to perform off-node allocations for other (i.e. non-tmpfs)
> memory needs.
>
> Tightly synchronized HPC applications with large (on the order of
> a single node's total RAM) per-task memory requirements are an example
> of a type of application which benefits from this change. Other
> types of workloads may prefer local tmpfs allocations, thus a mount
> option is provided.
>
> The new mount option is "interleave=", and defaults to 0. Any non-zero
> setting turns on interleaving. Interleaving behavior can be changed
> via a remount operation.
Looks good to me, though I don't really know that area of code very well.
Hopefully Hugh or someone can give it a better review.
Thanks for doing that,
M.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-11-08 20:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 1:07 Brent Casavant
2004-11-02 1:43 ` Dave Hansen
2004-11-02 9:13 ` Andi Kleen
2004-11-02 15:46 ` Martin J. Bligh
2004-11-02 15:55 ` Andi Kleen
2004-11-02 16:55 ` Martin J. Bligh
2004-11-02 22:17 ` Brent Casavant
2004-11-02 22:51 ` Martin J. Bligh
2004-11-03 1:12 ` Brent Casavant
2004-11-03 1:30 ` Martin J. Bligh
2004-11-03 8:44 ` Hugh Dickins
2004-11-03 9:01 ` Andi Kleen
2004-11-03 16:32 ` Brent Casavant
2004-11-03 21:00 ` Martin J. Bligh
2004-11-08 19:58 ` Brent Casavant
2004-11-08 20:57 ` Martin J. Bligh [this message]
2004-11-09 19:04 ` Hugh Dickins
2004-11-09 20:09 ` Martin J. Bligh
2004-11-09 21:08 ` Hugh Dickins
2004-11-09 22:07 ` Martin J. Bligh
2004-11-10 2:41 ` Brent Casavant
2004-11-10 14:20 ` Hugh Dickins
2004-11-11 19:48 ` Hugh Dickins
2004-11-11 23:10 ` Brent Casavant
2004-11-15 22:07 ` Brent Casavant
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='263890000.1099947448@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=ak@suse.de \
--cc=bcasavan@sgi.com \
--cc=colpatch@us.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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