linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ethan Solomita <solo@google.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Paul Jackson <pj@sgi.com>, linux-mm@kvack.org
Subject: Re: cpusets vs. mempolicy and how to get interleaving
Date: Fri, 17 Aug 2007 18:51:52 -0700	[thread overview]
Message-ID: <46C650B8.6040004@google.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708171805340.15278@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Fri, 17 Aug 2007, Ethan Solomita wrote:
> 
>> 	Ideally, we want a task to express its preference for interleaved
>> memory allocations without having to provide a list of nodes. The kernel will
>> automatically round-robin amongst the task's mems_allowed.
> 
> You can do that by writing 1 to /dev/cpuset/<cpuset>/memory_spread_page

	Sorry, also noticed that the above doesn't affect anonymous pages, just 
page cache, and we'd want interleaved anonymous pages.
	-- Ethan

--
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:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2007-08-18  1:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-18  0:22 Ethan Solomita
2007-08-18  0:29 ` Ethan Solomita
2007-08-19 10:18   ` David Rientjes
2007-08-20  0:53     ` Ethan Solomita
2007-08-20  2:34       ` Paul Jackson
2007-08-20  5:47         ` Ethan Solomita
2007-08-20  5:53           ` Paul Jackson
2007-08-20  8:10             ` David Rientjes
2007-08-20 18:25               ` Paul Jackson
2007-08-20 18:28               ` Ethan Solomita
2007-08-20 18:40                 ` David Rientjes
2007-08-20 19:50                   ` Ethan Solomita
2007-08-20 19:07           ` Christoph Lameter
2007-08-21 14:14             ` Lee Schermerhorn
2007-08-18  1:07 ` Christoph Lameter
2007-08-18  1:51   ` Ethan Solomita [this message]

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=46C650B8.6040004@google.com \
    --to=solo@google.com \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.org \
    --cc=pj@sgi.com \
    /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