[lkml]   [2003]   [Jan]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Lse-tech] Re: NUMA scheduler 2nd approach
> Erich,
> I played with this today on my 4 node (16 CPU) NUMAQ. Spent most
> of the time working with the first three patches. What I found was
> that rebalancing was happening too much between nodes. I tried a
> few things to change this, but have not yet settled on the best
> approach. A key item to work with is the check in find_busiest_node
> to determine if the found node is busier enough to warrant stealing
> from it. Currently the check is that the node has 125% of the load
> of the current node. I think that, for my system at least, we need
> to add in a constant to this equation. I tried using 4 and that
> helped a little.



+static int find_busiest_node(int this_node)
+ int i, node = this_node, load, this_load, maxload;
+ this_load = maxload = atomic_read(&node_nr_running[this_node]);
+ for (i = 0; i < numnodes; i++) {
+ if (i == this_node)
+ continue;
+ load = atomic_read(&node_nr_running[i]);
+ if (load > maxload && (4*load > ((5*4*this_load)/4))) {
+ maxload = load;
+ node = i;
+ }
+ }
+ return node;

You changed ((5*4*this_load)/4) to:
(4+(5*4*(this_load)/4)) ?

We def need some constant to avoid low load ping pong, right?

Finally I added in the 04 patch, and that helped
> a lot. Still, there is too much process movement between nodes.

perhaps increase INTERNODE_LB?

-Andrew Theurer

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:32    [W:0.135 / U:1.140 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site