linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jack Steiner <steiner@sgi.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] - Randomize node rotor used in cpuset_mem_spread_node()
Date: Wed, 28 Apr 2010 15:40:34 -0700	[thread overview]
Message-ID: <20100428154034.fb823484.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100428150432.GA3137@sgi.com>

On Wed, 28 Apr 2010 10:04:32 -0500
Jack Steiner <steiner@sgi.com> wrote:

> Some workloads that create a large number of small files tend to assign
> too many pages to node 0 (multi-node systems). Part of the reason is that
> the rotor (in cpuset_mem_spread_node()) used to assign nodes starts
> at node 0 for newly created tasks.

And, presumably, your secret testcase forks lots of subprocesses which
do the file creation?

> This patch changes the rotor to be initialized to a random node number
> of the cpuset.

Why random as opposed to, say, inherit-rotor-from-parent?

> Index: linux/arch/x86/mm/numa.c
> ===================================================================
> --- linux.orig/arch/x86/mm/numa.c	2010-04-28 09:44:52.422898844 -0500
> +++ linux/arch/x86/mm/numa.c	2010-04-28 09:49:39.282899779 -0500
> @@ -2,6 +2,7 @@
>  #include <linux/topology.h>
>  #include <linux/module.h>
>  #include <linux/bootmem.h>
> +#include <linux/random.h>
>  
>  #ifdef CONFIG_DEBUG_PER_CPU_MAPS
>  # define DBG(x...) printk(KERN_DEBUG x)
> @@ -65,3 +66,19 @@ const struct cpumask *cpumask_of_node(in
>  }
>  EXPORT_SYMBOL(cpumask_of_node);
>  #endif
> +
> +/*
> + * Return the bit number of a random bit set in the nodemask.
> + *   (returns -1 if nodemask is empty)
> + */
> +int __node_random(const nodemask_t *maskp)
> +{
> +	int w, bit = -1;
> +
> +	w = nodes_weight(*maskp);
> +	if (w)
> +		bit = bitmap_find_nth_bit(maskp->bits,
> +			get_random_int() % w, MAX_NUMNODES);
> +	return bit;
> +}
> +EXPORT_SYMBOL(__node_random);

I suspect random32() would suffice here.  It avoids depleting the
entropy pool altogether.

> +
> +/**
> + * bitmap_find_nth_bit(buf, ord, bits)
> + *	@buf: pointer to bitmap
> + *	@n: ordinal bit position (n-th set bit, n >= 0)
> + * @nbits: number of bits in the bitmap
> + *
> + * find the Nth bit that is set in the bitmap
> + * Value of @n should be in range 0 <= @n < weight(buf), else
> + * results are undefined.
> + *
> + * The bit positions 0 through @bits are valid positions in @buf.
> + */
> +int bitmap_find_nth_bit(const unsigned long *bitmap, int n, int bits)
> +{
> +	return bitmap_ord_to_pos(bitmap, n, bits);
> +}
> +EXPORT_SYMBOL(bitmap_find_nth_bit);

This does nothing apart from consume more stack?  Better to rename
bitmap_ord_to_pos() and export it.

--
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:[~2010-04-28 22:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 13:12 [PATCH] - Randomize node rotor used in cpuset_mem_spread_node() Jack Steiner
2010-04-28 15:04 ` [PATCH v2] " Jack Steiner
2010-04-28 22:40   ` Andrew Morton [this message]
2010-04-28 23:04     ` Matt Mackall
2010-04-28 23:12       ` Andrew Morton
2010-04-28 23:22         ` Stephen Hemminger
2010-04-28 23:28         ` Matt Mackall
2010-04-29  3:57     ` Robin Holt
2010-04-29 20:08     ` Jack Steiner
2010-04-29 20:09     ` [PATCH v3] " Jack Steiner

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=20100428154034.fb823484.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=steiner@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;
as well as URLs for NNTP newsgroup(s).