All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Mike Travis <travis@sgi.com>,
	"David S. Miller" <davem@davemloft.net>,
	linux kernel <linux-kernel@vger.kernel.org>,
	Christoph Lameter <cl@linux-foundation.org>,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH] percpu_counter: FBC_BATCH might be too big
Date: Fri, 05 Dec 2008 17:40:43 +0100	[thread overview]
Message-ID: <1228495243.24126.1.camel@twins> (raw)
In-Reply-To: <4939513C.3090101@cosmosbay.com>

On Fri, 2008-12-05 at 17:05 +0100, Eric Dumazet wrote:
> For NR_CPUS >= 16 values, FBC_BATCH is 2*NR_CPUS
> 
> Considering more and more distros are using high NR_CPUS values,
> it makes sense to use a more sensible value for FBC_BATCH.
> 
> A sensible value is 2*num_online_cpus(), with a minimum value of 32
> (This minimum value helps branch prediction in __percpu_counter_add())
> 
> We already have a hotcpu notifier, so we can adjust FBC_BATCH dynamically.

Agreed, that is one of the reasons the proportion code doesn't use the
FBC_BATCH stuff.

Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>

> Signed-off-by: Eric Dumazet <dada1@cosmosbay.com>
> ---
>  include/linux/percpu_counter.h |    6 +-----
>  lib/percpu_counter.c           |   14 +++++++++++++-
>  2 files changed, 14 insertions(+), 6 deletions(-)
> 
> diff --git a/include/linux/percpu_counter.h b/include/linux/percpu_counter.h
> index 9007ccd..c42a184 100644
> --- a/include/linux/percpu_counter.h
> +++ b/include/linux/percpu_counter.h
> @@ -24,11 +24,7 @@ struct percpu_counter {
>  	s32 *counters;
>  };
>  
> -#if NR_CPUS >= 16
> -#define FBC_BATCH	(NR_CPUS*2)
> -#else
> -#define FBC_BATCH	(NR_CPUS*4)
> -#endif
> +extern int FBC_BATCH;
>  
>  int percpu_counter_init(struct percpu_counter *fbc, s64 amount);
>  int percpu_counter_init_irq(struct percpu_counter *fbc, s64 amount);
> diff --git a/lib/percpu_counter.c b/lib/percpu_counter.c
> index a866389..2fcf943 100644
> --- a/lib/percpu_counter.c
> +++ b/lib/percpu_counter.c
> @@ -114,6 +114,16 @@ void percpu_counter_destroy(struct percpu_counter *fbc)
>  }
>  EXPORT_SYMBOL(percpu_counter_destroy);
>  
> +int FBC_BATCH __read_mostly = 32;
> +EXPORT_SYMBOL(FBC_BATCH);
> +
> +static void compute_batch_value(void)
> +{
> +	int nr = num_online_cpus();
> +
> +	FBC_BATCH = max(32, nr*2);
> +}
> +
>  #ifdef CONFIG_HOTPLUG_CPU
>  static int __cpuinit percpu_counter_hotcpu_callback(struct notifier_block *nb,
>  					unsigned long action, void *hcpu)
> @@ -121,6 +131,7 @@ static int __cpuinit percpu_counter_hotcpu_callback(struct notifier_block *nb,
>  	unsigned int cpu;
>  	struct percpu_counter *fbc;
>  
> +	compute_batch_value();
>  	if (action != CPU_DEAD)
>  		return NOTIFY_OK;
>  
> @@ -139,11 +150,12 @@ static int __cpuinit percpu_counter_hotcpu_callback(struct notifier_block *nb,
>  	mutex_unlock(&percpu_counters_lock);
>  	return NOTIFY_OK;
>  }
> +#endif
>  
>  static int __init percpu_counter_startup(void)
>  {
> +	compute_batch_value();
>  	hotcpu_notifier(percpu_counter_hotcpu_callback, 0);
>  	return 0;
>  }
>  module_init(percpu_counter_startup);
> -#endif

  reply	other threads:[~2008-12-05 16:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 16:05 [PATCH] percpu_counter: FBC_BATCH might be too big Eric Dumazet
2008-12-05 16:40 ` Peter Zijlstra [this message]
2008-12-05 20:32 ` David Miller
2008-12-07  9:25 ` [PATCH, take2] " Eric Dumazet
2008-12-07 17:09   ` Andrew Morton
2008-12-07 18:30     ` Eric Dumazet
2008-12-07 18:30       ` Eric Dumazet
2008-12-08  4:32       ` Andrew Morton
2008-12-08  8:05         ` [PATCH] percpu_counter: FBC_BATCH should be a variable Eric Dumazet
2008-12-08  8:05           ` Eric Dumazet
2008-12-08  8:19           ` Andrew Morton

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=1228495243.24126.1.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=dada1@cosmosbay.com \
    --cc=davem@davemloft.net \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=travis@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.