public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Anton Blanchard <anton@samba.org>
Cc: manfred@colorfullife.com, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use numa policy API for boot time policy
Date: Sat, 5 Jun 2004 12:22:39 +0200	[thread overview]
Message-ID: <20040605122239.4a73f5e8.ak@suse.de> (raw)
In-Reply-To: <20040605023211.GA16084@krispykreme>

On Sat, 5 Jun 2004 12:32:12 +1000
Anton Blanchard <anton@samba.org> wrote:

>  
> Hi,
> 
> > That's correct. It will only work for order 0 allocations.
> > 
> > But it sounds quite bogus anyways to move the complete hash tables
> > to another node anyways. It would probably be better to use vmalloc() 
> > and a interleaving mapping for it. Then you would get the NUMA bandwidth 
> > benefit even for accessing single tables.
> 
> I posted some before and after numbers when we merged Manfreds patch,
> it would be interesting to see the same thing with your patch applied.
> 
> Im not only worried about NUMA bandwidth but keeping the amount of
> memory left in all the nodes reasonably even. Allocating all the big
> hashes on node 0 will decrease that balance.

It would be a one liner change to allow process policy interleaving 
for orders > 0 in mempolicy. But I'm not sure how useful it is, since
the granuality would be really bad.

Have you ever tried to switch to implement a vmalloc_interleave() for these
tables instead? My bet is that it will perform better.

-Andi

  reply	other threads:[~2004-06-05 10:24 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 [this message]
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
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=20040605122239.4a73f5e8.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.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