public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Andi Kleen <ak@suse.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use numa policy API for boot time policy
Date: Sat, 05 Jun 2004 12:20:53 +0200	[thread overview]
Message-ID: <40C19E85.7090809@colorfullife.com> (raw)
In-Reply-To: <20040605041813.75e2d22d.ak@suse.de>

Andi Kleen wrote:

>On Sat, 05 Jun 2004 03:56:53 +0200
>Manfred Spraul <manfred@colorfullife.com> wrote:
>  
>
>>Does it work for order != 0 allocations? It's important that the big 
>>hash tables do not end up all in node 0. AFAICS alloc_pages_current() 
>>calls interleave_nodes() only for order==0 allocs.
>>    
>>
>
>That's correct. It will only work for order 0 allocations.
>
>  
>
What's the purpose of the "&& order == 0)" test for MPOL_INTERLEAVE in 
alloc_pages_current?
What would break if it's removed?

And what about in_interrupt() allocations? During boot everything should 
be interleaved - I'd modify default_policy to MPOL_INTERLEAVE instead of 
setting process affinity.

--
    Manfred

  parent reply	other threads:[~2004-06-05 10:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-05  1:43 [PATCH] Use numa policy API for boot time policy Andi Kleen
2004-06-05  1:56 ` Manfred Spraul
2004-06-05  2:18   ` Andi Kleen
2004-06-05  2:32     ` Anton Blanchard
2004-06-05 10:22       ` Andi Kleen
2004-06-05 10:48         ` Andi Kleen
2004-06-09 15:44         ` Anton Blanchard
2004-06-09 15:56           ` Andi Kleen
2004-06-09 16:12             ` Anton Blanchard
2004-06-05 10:20     ` Manfred Spraul [this message]
2004-06-05 10:33       ` Andi Kleen

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=40C19E85.7090809@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --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