linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Brent Casavant <bcasavan@sgi.com>, Andi Kleen <ak@suse.de>,
	"Adam J. Richter" <adam@yggdrasil.com>,
	colpatch@us.ibm.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH] Use MPOL_INTERLEAVE for tmpfs files
Date: Tue, 09 Nov 2004 14:07:21 -0800	[thread overview]
Message-ID: <477220000.1100038041@flay> (raw)
In-Reply-To: <Pine.LNX.4.44.0411092056090.5291-100000@localhost.localdomain>

--On Tuesday, November 09, 2004 21:08:11 +0000 Hugh Dickins <hugh@veritas.com> wrote:

> On Tue, 9 Nov 2004, Martin J. Bligh wrote:
>>  
>> > I'm irritated to realize that we can't change the default for SysV
>> > shared memory or /dev/zero this way, because that mount is internal.
>> 
>> Boggle. shmem I can perfectly understand, and have been intending to
>> change for a while. But why /dev/zero ? Presumably you'd always want
>> that local?
> 
> I was meaning the mmap shared writable of /dev/zero, to get memory
> shared between parent and child and descendants, a restricted form
> of shared memory.  I was thinking of them running on different cpus,
> you're suggesting they'd at least be on the same node.  I dare say,
> I don't know.  I'm not desperate to be able to set some other mpol
> default for all of them (and each object can be set in the established
> way), just would have been happier if the possibility of doing so came
> for free with the mount option work.

Oh yeah ... the anon mem allocator trick. Mmmm. Not sure that should
have a different default than normal alloced memory, but either way,
what you're suggesting makes a whole lot more sense to me know than
just straight /dev/zero ;-)

Thanks for the explanation.

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>

  reply	other threads:[~2004-11-09 22:07 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
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 [this message]
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=477220000.1100038041@flay \
    --to=mbligh@aracnet.com \
    --cc=adam@yggdrasil.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