public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: lse-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] subset zonelists and big numa friendly mempolicy MPOL_MBIND
Date: Wed, 4 Aug 2004 15:33:10 -0700	[thread overview]
Message-ID: <20040804153310.618413cb.pj@sgi.com> (raw)
In-Reply-To: <20040803020805.060620fa.ak@suse.de>

A couple of days ago, Andi wrote:
> My first reaction that if you really want to do that, just pass
> the policy node bitmap to alloc_pages and try_to_free_pages
> and use the normal per node zone list with the bitmap as filter. 

I have coded your suggestion up, and indeed, it is much simpler

I added an optional (#ifdef CONFIG_CPUSET) "mems_allowed" field to the
task_struct, and filter zones on this mask (if not in_interrupt()) in
the page allocation and free'ing code.

Thank-you.  I think you're right, and it's the way to go.

I will be posting a full cpuset patch that includes this change on
lse-tech and lkml, hopefully in a few hours.  I will be most grateful
for any further feedback.

Providing support for dividing very large systems into subsets of
nodes (cpu and memory), in order to obtain good memory locality and
good isolation of big jobs from each other, is essential to the success
of certain high end Linux users.

-- 
                          I won't rest till it's the best ...
                          Programmer, Linux Scalability
                          Paul Jackson <pj@sgi.com> 1.650.933.1373

      parent reply	other threads:[~2004-08-04 22:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02 23:35 [PATCH] subset zonelists and big numa friendly mempolicy MPOL_MBIND Paul Jackson
2004-08-03  0:08 ` Andi Kleen
2004-08-03  2:14   ` Paul Jackson
2004-08-03  7:58     ` [Lse-tech] " Paul Jackson
2004-08-04 22:33   ` Paul Jackson [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=20040804153310.618413cb.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    /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